Fetch a single knowledge-base entry verbatim by its stable id (e.g. "eng_000229f438f7cebd"). Deterministic retrieval — returns the full record plus a content_hash and kb_snapshot for reproducible citation.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Stable knowledge entry id, e.g. eng_... or soc_... |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnly/idempotent annotations, the description adds that retrieval is deterministic and that the response includes a content_hash and kb_snapshot for reproducible citation, giving useful behavioral context.
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 compact sentences with high information density. Zero waste, front-loaded with the core action.
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?
For a single-id fetch with no output schema, the description explains the return contents (full record plus hash/snapshot) and deterministic behavior. Could mention not-found behavior, but that's a minor gap.
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 sole parameter 'id' is fully described in the schema with format examples; the description reinforces this with another concrete example but does not add significant new meaning beyond what the schema already provides.
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 uses a specific verb 'Fetch' with a clear resource 'a single knowledge-base entry', qualifies it with 'verbatim' and 'by its stable id', and provides an id example. This clearly differentiates it from sibling search tools.
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 description implies the tool is for retrieving an exact entry when you have a stable id, emphasizing deterministic retrieval for reproducible citation. However, it does not explicitly state when not to use it or mention alternative tools.
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.
Most tools have clearly distinct purposes, but the three search tools (search, search_global, batch_search) and the two relation tools (related, isomorph) could cause initial confusion despite clear descriptions. Overall boundaries are clear enough that agents should select correctly with careful reading.
Every tool uses the consistent coldstate_ prefix followed by a descriptive verb_noun pattern (e.g., batch_search, browse_documents, list_indexes). The naming is uniform and predictable, making the toolset easy to navigate.
At 16 tools, the server sits at the upper edge of what feels reasonable, and the calibration guidance flags 16-25 as heavy. However, each tool serves a distinct function in the knowledge-search lifecycle, so the count is defensible but still slightly high for a single server.
The toolset covers the full read-only knowledge workflow: searching, browsing, fetching, citing, verifying, explaining, resolving, and exploring relations. It also includes meta-tools for capabilities, domains, snapshots, and statistics, leaving no obvious gaps for its stated purpose.