Get the current knowledge-base snapshot/version id. Pin this kb_snapshot for reproducibility: the same query against the same kb_snapshot returns identical results.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and not destructive. The description adds the key behavioral trait that the same query against the same snapshot returns identical results, and clarifies it returns the current version ID. This goes beyond the annotations by specifying the reproducibility contract.
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 two sentences, front-loaded with the primary action, and every word earns its place. It concisely conveys purpose and behavioral guarantee without redundancy.
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?
As a simple retrieval tool with no parameters and strong annotations, the description fully covers purpose, usage context, and reproducibility. The lack of output schema is acceptable given the simplicity of the tool and the clear description of what it returns.
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, so schema coverage is trivially 100%. The description mentions kb_snapshot as a concept but not as an input, and since there are no parameters, no additional parameter semantics are needed. Baseline 4 is appropriate.
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 clearly states the tool retrieves the current knowledge-base snapshot/version ID using the verb 'Get' and a specific resource. It distinguishes from sibling tools that perform searches, fetches, or other operations, and adds the purpose of reproducibility.
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?
It implies when to use the tool: when a stable snapshot ID is needed for reproducible queries. It explains the behavioral guarantee that the same snapshot yields identical results, but does not explicitly name alternative tools or exclusions, which is acceptable for a zero-parameter tool.
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.