Return attestation-chain continuity status, event count, latest event hashes, and latest timestamp when available.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a read-only operation via 'Return', but does not explicitly state side effects or permissions; no annotations to rely on.
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?
Single, concise sentence with no fluff; clearly structured.
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?
Covers all key return items and the 'when available' caveat; sufficient for a simple getter with no parameters.
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?
No parameters exist, so the description adequately covers them by omission; baseline for 0 params is 4.
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 purpose: return chain health data, specifying the exact items returned.
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 on when to use this tool versus the many sibling get tools; lacks explicit when/when-not or alternatives.
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 are clearly distinct, targeting specific documents or endpoints (e.g., identity, capabilities, JWKS, receipts). However, some overlap exists among discovery-related tools (e.g., get_agent_discovery, get_agent_identity, get_capabilities, get_marketplace_listing) that could cause confusion about which to use for a given purpose.
All tool names follow a consistent pattern: 'hodlxxi_get_' or 'hodlxxi_verify_' followed by a descriptive noun phrase. The verbs are consistent (get/verify) and the nouns are specific, making the naming predictable and uniform.
With 26 tools, the count is slightly above the typical well-scoped range (3-15) but still reasonable for a read-only server that exposes a wide array of public documents and metadata. Each tool serves a distinct purpose, so the count is justified, though it borders on heavy.
The server covers a comprehensive set of read-only operations for its domain: identity, capabilities, skills, receipts, trust events, OAuth/OIDC metadata, and verification. Minor gaps exist, such as no tool for listing all covenants or reports (only get by identifier), but the core surface is well-covered.