revocations
Published revocations of dealing codes and mandates — audit trail of who lost authority when (carrier rule 5: nothing is hidden).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
wire
by net.csclear
TDQS
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool provides an audit trail of 'who lost authority when' and cites a rule about transparency. This implies the tool is read-only and trustworthy. However, it does not explicitly state permissions or 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.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads the main purpose. The parenthetical adds flavor but is not essential. Overall, it is concise and clear without wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no parameters and no output schema, the description provides sufficient context about what the tool returns. It does not describe the format of the output (e.g., list, details), but for a simple audit trail tool, the description is adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, so the description does not need to explain parameters. It adds meaning by defining the content of the tool's output (revocations, audit trail). Since there are zero parameters, the baseline is 4, and the description adequately compensates.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'revocations of dealing codes and mandates' as an audit trail. It specifies the resource (dealing codes and mandates) and the action (published revocations). The parenthetical 'carrier rule 5: nothing is hidden' adds context. It distinguishes from sibling 'mandates' which likely shows current mandates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance is provided. However, the description implies it is for checking published revocations. The sibling tool 'mandates' suggests an alternative, but no direct comparison is made.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a distinct aspect of the dealing wire (e.g., conv_status vs. deal_status, directory vs. instruments), with no obvious overlap. Descriptions clearly differentiate their purposes.
Naming Consistency4/5
Tool names are mostly snake_case and descriptive, but vary between noun phrases (e.g., 'about', 'montage') and verb phrases (e.g., 'post_axe', 'send_call'). The pattern is not fully uniform but remains clear and readable.
Tool Count5/5
With 18 tools, the server covers documentation, status queries, listing, and actions for a complex protocol. The count is well-scoped, avoiding both excess and insufficiency.
Completeness5/5
The tool surface provides full lifecycle coverage: reading schemas, posting axes, sending envelopes, polling rings, and inspecting deals and conversations. No obvious gaps for the stated purpose of agent-based dealing on the wire.