Retrieve every live dreamDEX perpetual market on the Somnia Hideki testnet, including pool addresses, margin requirements, and order-size rules, so agents can plan trades with correct constraints.
List all dreamDEX perpetual markets live on the Somnia Hideki testnet, with pool addresses, margin requirements and order-size rules.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does useful work by previewing the payload (pool addresses, margin requirements, order-size rules) in the absence of an output schema, and 'List' implies a safe read. It does not state auth requirements, testnet-only limitations, or whether results are paginated.
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 front-loaded sentence with no filler: scope, environment, and payload contents in one pass.
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-param read tool with no output schema and no annotations, the description supplies the environment context and the shape of the returned data. Only operational details such as pagination or testnet constraints are missing.
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 takes zero parameters, so the schema baseline of 4 applies; there is nothing further the description could clarify about inputs.
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?
States a specific verb and resource ('List all dreamDEX perpetual markets') plus the environment (Somnia Hideki testnet) and the returned fields. The plural 'all markets' implicitly contrasts with the singular sibling get_market, though it never names that alternative.
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 scope 'all ... markets' versus get_market's single-market retrieval is implied by naming and the sibling list, but there is no explicit when-to-use guidance, prerequisites, or exclusion. Usage must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.