Skip to content
DE EN

Knowledge and code

Find knowledge: search_knowledge

Searches a project's notes and documents by their title, not their text.

Argument Meaning
q required, the search term
type only note or only document
page, per_page page, at most 100 per page

Each hit carries a ready link of the form lalabase://note/<uuid>. How to use it is covered under link documentation. If you may not read one kind, it simply returns no hits.

Code context

If a project has a connected repository, Lalabase knows its structure. These tools go from large to small:

Tool Returns Arguments
get_project_vision a summary of what the project is and what it consists of none
list_capabilities the capabilities, coherent feature areas none
get_capability_details one capability with description and key modules capability_id
search_code_symbols classes, modules and methods that fit a question query, limit (default 10, at most 25)
get_symbol_details signature, file, lines and language of a symbol qualified_name, such as Chatpost#destroy

These tools return no source code: get_symbol_details names the place, not its content. If the code is on your machine, the agent reads it there.

Prerequisites

The code tools answer only for projects whose repository you may see yourself. The token alone is not enough, and without that right the project counts as not found here. If no code has been read in yet, the answer says so.

The five code tools also need your organisation's AI: a repository is read in only with AI switched on. Without it, they keep answering that nothing has been read in yet. search_code_symbols also uses the AI on every search and is refused if it has been switched off since or a key is missing. search_knowledge works without AI.

All tools on this page need a project_id.