list_knowledgeList all knowledge units (concepts on agentic & enterprise AI) with slug, category, title, summary and Evidence-First provenance. Use this to browse the domain; use search when you have a question rather than a slug.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Language of the returned body. Default: en. |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| results | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only and idempotent behavior, lowering the burden. The description adds that the tool returns 'all' knowledge units and lists the included fields, which helps set expectations for the response beyond the annotations.
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?
Two sentences, first front-loads the core function, second provides usage guidance. No redundancy or filler.
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 an output schema present and good annotations, the description covers purpose, usage, and alternatives. It also includes the provenance aspect which is a likely key differentiator for this tool.
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 single `locale` parameter is fully described in the input schema (coverage 100%) including its enum values and default. The description adds no additional parameter semantics, so the baseline of 3 applies.
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 specific action and resource: 'List all knowledge units (concepts on agentic & enterprise AI) with slug, category, title, summary and Evidence-First provenance.' It clearly distinguishes this from the 'search' sibling by positioning it as a browsing tool, making the purpose unambiguous.
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?
'Use this to browse the domain; use `search` when you have a question rather than a slug' explicitly states when to use this tool and when to use an alternative. This is textbook usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct operation and identifier: search is the entry point, list_* returns browsing summaries, get_* returns a single unit, get_related traverses the graph, and get_overview maps the corpus. Even the similar get_homeric_* trio is cleanly separated by episode/place/route.
All names follow snake_case verb_noun: get_* for singular retrieval, list_* for enumeration, plus search. get_related and get_overview are the only deviations but remain predictable read operations.
21 tools is above the typical 3-15 range, but the count is justified by the number of distinct corpora and the consistent list/get pairing for each; there are no redundant tools, so it is only slightly heavy.
The server offers a complete read-side lifecycle for this knowledge corpus: overview, search, list, get, and graph traversal. For a read-only knowledge server, there are no obvious dead ends; coverage of claims, patterns, architectures, governance, handbook and Homeric atlas is thorough.