Skip to main content
Glama
Sign In
tas-guard

tas-guard

by intoApex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cancel_order_by_id

Destructive

Cancel a single demo order using its order ID. Use this to stop an unwanted or pending demo trade before it executes.

Instructions

Cancel one demo order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "order_id": "<order_id>"
    },
    "name": "cancel_order_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

destructiveHint=true already tells the agent this is a destructive operation, so safety is covered by annotations. The description adds nothing beyond that — no irreversibility warning, no permission/auth requirements, no error or partial-failure behavior for a cancel of an unknown or already-cancelled order.

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?

A single front-loaded sentence with no padding or filler. It is efficient, though the terseness is under-specification rather than true conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, parameter-taking tool with no output schema and zero parameter documentation, the description leaves an agent without enough to invoke it correctly. It does not identify the order_id source or say what happens on success or failure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required order_id parameter, and the description does not compensate at all — no format, source, or example for the identifier. The agent cannot tell where order_id comes from (get_orders presumably) or what shape is valid.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Cancel one demo order'), and the word 'one' implicitly contrasts with the sibling cancel_all_orders. However, it never names that sibling or explicitly marks the single-vs-bulk boundary, and the stray qualifier 'demo' leaves ambiguity about whether it works on real orders.

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?

No when-to-use guidance, no conditions distinguishing it from cancel_all_orders or close_all_positions, and no prerequisites stated. The agent must infer the routing entirely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools