paper_cancel_all
Cancel all open paper trading orders simultaneously to reset your simulated trading environment for strategy adjustments.
Instructions
Cancel all paper trading orders
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Cancel all open paper trading orders simultaneously to reset your simulated trading environment for strategy adjustments.
Cancel all paper trading orders
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It only states the action but does not explain whether the cancellation is reversible, if confirmation is needed, or what happens to canceled orders. The omission leaves the agent without important context.
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 a single, clear sentence that states the tool's purpose without any unnecessary words. It is front-loaded and concise.
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 simple tool with no parameters and no output schema, the description is adequate but still lacks context. An agent might benefit from knowing whether the action is irreversible or if it returns a list of canceled orders, but the description only covers the basic purpose.
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?
There are no parameters (0 parameters, schema coverage 100%). Per the rules, a baseline of 4 is appropriate because the description adds no parameter information, but none is needed.
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 clearly states the action 'Cancel all paper trading orders', specifying the verb 'Cancel' and the resource 'all paper trading orders'. It distinguishes from sibling tools like 'paper_cancel' (cancels a specific order) and 'paper_reset' (resets everything).
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 provides no guidance on when to use this tool versus its alternatives. For example, it doesn't indicate that 'paper_cancel' should be used for individual orders, nor does it mention any prerequisites or side effects.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ibidathoillah/indodax-cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server