Return public NIP-17/NIP-59 messaging policy metadata, including intake status, custody limitations, accepted kind, and size ceiling.
| 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?
With no annotations provided, the description carries the full burden. It discloses the operation is a public metadata read ('Return public...') and enumerates the content categories, giving a clear picture of what the tool offers without claiming any side effects.
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?
A single, well-structured sentence that front-loads the purpose and packs the key metadata categories into a compact list. No filler words or redundant content.
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 zero-parameter tool with an output schema, the description is complete: it states the resource, the public nature, and the included metadata fields. Nothing additional is needed for an agent to invoke the tool 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 tool has zero parameters, so there is no parameter semantics to convey. The description correctly avoids mentioning any parameters, matching the empty schema.
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 ('Return') and identifies a precise resource ('public NIP-17/NIP-59 messaging policy metadata') with listed fields (intake status, custody limitations, accepted kind, size ceiling). This clearly distinguishes it from sibling tools like get_agent_identity or get_capabilities.
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?
Provides clear context: it is for retrieving public DM policy metadata for NIP-17/NIP-59. It doesn't explicitly state when to use alternatives, but the specification of the policy type provides enough context for a zero-parameter getter.
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.