Roll all pending breadcrumbs into a new sealed epoch with a Merkle root. Returns { epoch_index, merkle_root, block_count, epoch_hash }. Call this at the end of a session to produce a tamper-evident compliance snapshot.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the operation 'seals' the epoch (implying finality/irreversibility), uses a Merkle root for tamper evidence, and returns a structured result. This goes beyond a simple 'rolls breadcrumbs' and gives meaningful behavioral context about the irreversible, compliance-oriented nature of the action.
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 result. Every sentence adds value: the first states the operation and output; the second specifies when to invoke it and why. There is 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?
Despite lacking an output schema and annotations, the description covers the essential aspects: what the tool does (rolls pending breadcrumbs into a sealed epoch), when to use it (end of session), what it returns (epoch_index, merkle_root, block_count, epoch_hash), and the broader purpose (tamper-evident compliance snapshot). This is sufficient for an agent to invoke it correctly without additional structured information.
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 the baseline is 4. The description effectively explains the scope via 'all pending breadcrumbs' and the return values, meaning there is no parameter ambiguity. No additional parameter documentation needed.
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 'Roll' with a clear resource: 'all pending breadcrumbs into a new sealed epoch with a Merkle root.' It clearly distinguishes from siblings like gns_get_compliance_report or gns_verify_chain by describing a state-changing operation that seals data. The return fields are explicit, reinforcing the purpose.
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 provides explicit guidance: 'Call this at the end of a session to produce a tamper-evident compliance snapshot.' This clearly indicates when to use the tool. It does not explicitly mention alternatives or when not to use it, but the context is distinct enough from sibling tools that usage intent is unambiguous.
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.
Each tool has a distinct purpose within its domain: gns_* tools handle compliance reporting, trust scoring, epoch rolling, and chain verification, while perception_* tools handle tile fetching, classification, embedding, and weather queries. Even similar tools like gns_get_compliance_report and gns_get_trust_score are clearly differentiated by scope (full report vs quick score).
The gns_* tools follow a consistent verb_noun pattern (get_compliance_report, get_trust_score, roll_epoch, verify_chain), but perception_* tools mix styles: perception_fetch_tile is verb_noun, perception_classify and perception_embed are just verbs, and perception_weather is a noun. The two prefixes (gns_ vs perception_) also introduce a split, though each group is internally readable.
Eight tools is well-scoped for a server that combines two related functions: AI-powered earth observation and cryptographic compliance auditing. Each tool serves a distinct role and there are no redundant utilities, making the count feel intentional and complete.
The core workflows are covered: fetch a tile, classify it, embed it (though not yet implemented), and weather queries for context, with a full compliance trail via breadcrumbs, epochs, and verification. The only notable gap is that perception_embed is explicitly marked as not implemented, leaving a placeholder in the tool surface, but the rest of the pipeline is functional.