Fetch the venue's Ed25519 public key and receipt semantics, returning the key hex and how to verify a ledger entry's receipt signature against it. Use this when the user wants to independently verify a settlement receipt rather than trust this server's word for it.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, and destructiveHint false. The description adds behavioral context about what is returned (key hex and receipt semantics) and the purpose of independent verification. While it doesn't mention rate limits or auth, the annotation coverage lowers the bar and the added detail is valuable.
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 action, and every sentence adds value. It avoids repetition of annotations and is highly efficient.
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 the simplicity of the tool (no parameters), the presence of an output schema, and rich annotations, the description fully covers the purpose, return content, and use case. It is complete without needing to explain return values in depth.
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 a baseline of 4 is appropriate. There is no need to describe parameter meanings, and the schema trivially covers all 100% of parameters.
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 and resource: 'Fetch the venue's Ed25519 public key and receipt semantics.' It clearly states the output (key hex and verification method) and distinguishes itself from siblings by emphasizing independent verification rather than trusting the server's word.
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 explicitly says when to use this tool: 'Use this when the user wants to independently verify a settlement receipt rather than trust this server's word for it.' This provides clear when-to-use guidance and implies when not to use it (when trusting the server's response is acceptable).
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 targets a distinct resource or action: fetching challenge, corpus, issue, ledger, market, params, key, settlement, solution; listing issues, tasks, solutions; preparing and submitting work; and describing the protocol. There is no overlap or ambiguity among them.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_*, list_*, prepare_*, submit_*, and describe_*. The pattern is uniform and predictable across the entire set.
With 15 tools, the surface is well-scoped for a domain that requires both read and write capabilities. Each tool contributes meaningfully without redundancy, and the count falls within the ideal 3-15 range.
The tool set provides full lifecycle coverage: understanding the write protocol, reading all relevant data (issues, markets, ledger, settlements, solutions, params), preparing work entries, and submitting them. There are no obvious gaps or dead ends for an agent to accomplish its goals.