List DIEM Agent Workers
list_diem_workersList bounded x402-paid workers, exact USDC prices, schemas, limits, and endpoints. This tool is free.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DIEM Agent Workers
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden. It discloses the tool is free and enumerates the output contents, implying a read-only listing. However, it does not explicitly state safety, side effects, or output format.
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?
Two short sentences, front-loaded with the action and content. No redundant phrases.
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 no output schema, the description clearly states what is returned: workers, prices, schemas, limits, and endpoints. It lacks format details, but for a simple list tool with no parameters, it 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 tool has zero parameters, so the baseline is 4. The description adds no parameter-specific information, which is appropriate.
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 uses the specific verb 'List' and names the resource 'bounded x402-paid workers', with detail on what is included (USDC prices, schemas, limits, endpoints). This distinguishes it from sibling tools 'prepare_diem_worker_call' and 'quote_diem_worker' which are action-oriented.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus the sibling tools. It only adds 'This tool is free,' which hints at cost but does not clarify selection criteria for listing vs preparing/quoting.
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
A4.1/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: listing workers, preparing a call, and quoting a price. There is no overlap or ambiguity between them.
Naming Consistency5/5
All tool names follow a consistent verb_diem_worker pattern: list, prepare, and quote. The naming is uniform and predictable.
Tool Count5/5
The server has three tools, which is well-scoped for its purpose of discovering, quoting, and preparing x402-paid worker calls. Each tool is essential and earns its place.
Completeness5/5
The tool set covers the full intended lifecycle: list available workers, get an exact price quote, and prepare the call for execution. Since execution is delegated to an external client, there are no significant gaps.