Every feed a client can drive a game from - corpus lanes by mined_from, the live global feeds, and the transport each is reachable on (REST, RSS, MCP, NATS subject). Stateless; takes no arguments.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral disclosure burden. It explicitly states 'Stateless; takes no arguments,' which confirms a read-only, no-argument operation. However, it leaves details like response representation, availability, or potential errors unspecified.
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-loads the main purpose, and packs content scoping and stateless/no-arguments traits into concise language without 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?
Given zero parameters and no output schema, the description adequately conveys what the tool returns: the complete feed set with transports. It does not specify the exact response structure, but for a simple, stateless catalog this is enough to select and invoke correctly.
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 input schema is empty with 0 parameters and 100% schema coverage, so the baseline is 4. The description's 'takes no arguments' matches the schema and adds no unnecessary parameter detail.
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 identifies a specific resource (all feeds a client can drive a game from) and scopes its contents (corpus lanes by mined_from, live global feeds, transport). It lacks an explicit action verb such as 'list' or 'return', and does not directly distinguish itself from sibling corpus tools like corpus_coverage.
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?
No guidance is provided on when to use this tool versus alternatives. The description merely defines the catalog; it does not state any conditions, exclusions, or names of sibling tools for routing an agent.
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.
Many verify_* tools are distinct, but there are overlapping clusters: math_court duplicates execute_2local_hamiltonian, route_spin_glass_manifold, and the quantum verifiers; project_affine_key, expose, verify_presented_pair, and the optional affine exposes in other tools blur together; weather and geometry tools also overlap. The detailed descriptions help a human, but an agent would likely struggle to choose between equivalent-seeming entry points.
Naming is mostly snake_case but otherwise inconsistent: some tools use dotted prefixes (atc.*, twin.robotics.*, weather.*), some use bare verbs (expose, lattice_op, math_court), some use noun phrases (corpus_bonds, feeds_catalog), and others mix prefixes with verbs (ide_rebuild_mesh, umc_resume). The verify_* family is consistent, but the overall set has no single predictable verb_noun pattern.
49 tools is far above the typical well-scoped server size and includes multiple near-duplicate paths to the same law (math_court, execute_*, route_*, verify_*). While not quite 50+, the count still feels like a sprawling kitchen-sink rather than a deliberate minimal surface.
The toolset covers a surprisingly wide range: QC verifiers, QMA laws, affine projections, corpus reads, weather, UMC state, and robotics IK. However, there are notable gaps for such a broad surface: no general court case lifecycle beyond expose/seal, no corpus content search, and no way to manage or update sealed artifacts; several areas have only entry-point coverage.