instruments
Every instrument on the network: registered specs (schema, oracle, expiry) + live axes + recent prints.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
wire
by net.csclear
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description fully carries the burden of behavioral disclosure. It clearly states that the tool returns registered specs, live axes, and recent prints, which is sufficient for a read-only list tool. However, it does not disclose any potential performance constraints or pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is well-structured and front-loaded with the key scope ('Every instrument on the network'). It conveys the essential information without waste, earning its place.
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?
Given the tool's simplicity (no parameters, no output schema), the description is nearly complete. It explains the three main components of the output. It could optionally mention if the list is paginated or sorted, but this is not critical for basic usage.
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 tool has zero parameters and 100% schema description coverage, so the baseline is 4. The description adds value beyond the schema by explaining what the returned data includes, which helps an agent understand the output.
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 it returns 'every instrument on the network' with three specific components: registered specs (schema, oracle, expiry), live axes, and recent prints. This precise verb+resource+scope clearly distinguishes it from siblings like 'instrument_schemas' (only schemas) and 'spec' (single instrument).
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?
The description implies usage when a comprehensive list of all instruments is needed but does not explicitly state when not to use it or provide comparisons to alternative tools like 'spec' or 'montage'. No exclusion criteria or prerequisites are mentioned.
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.