list_knowledge_librariesDiscover all accessible knowledge libraries with key statistics, helping you choose the right library for context expansion.
Lists all available knowledge libraries with their statistics.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| libraries | Yes | ||
| total_libraries | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that the result includes statistics, which is useful, but it does not disclose details like ordering, pagination, or access requirements. No contradiction exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. Every word contributes meaning, and the core action plus output scope are stated immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters, an output schema present, and annotations covering side-effect behavior, the description is complete enough for an agent to invoke the tool correctly. It communicates the tool's scope and result content without needing extra detail.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema description coverage is 100%, so there are no parameter gaps to compensate for. The description's mention of 'all available' and 'statistics' adds mild context about what a parameterless call returns, but its main value is simply confirming the scope.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb-resource pair: 'Lists all available knowledge libraries' and adds the output detail 'with their statistics.' It clearly contrasts with create/delete/query operations, although it does not explicitly differentiate from the overlapping sibling get_library_stats.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The usage context is implied: call this tool when you need an inventory of all knowledge libraries and their statistics. However, the description gives no explicit guidance about when to prefer this over get_library_stats or list-like alternatives, so the agent must infer the boundary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.