Skip to main content
Glama
Sign In
mt5-mcp

mt5-mcp

by vincentwongso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cancel_order

Cancel a pending order by ticket number, reducing exposure without additional approval.

Instructions

Cancel a pending order by ticket. No consent gate (reduces exposure).

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": {
      "ticket": "<ticket>"
    },
    "name": "cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions the action and that no consent gate exists, but does not explain side effects (e.g., order status changes), error handling, or idempotency behavior despite having an idempotency_key parameter.

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 sentences, front-loaded with key information. No superfluous text. Every sentence adds value.

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?

Given the tool's simplicity (2 parameters, no output schema), the description lacks detail on idempotency key use, return values, and error conditions. Without annotations, it feels incomplete for an agent to confidently invoke.

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 coverage is 0%, so the description must compensate. It explains the 'ticket' parameter as the order identifier, but does not explain 'idempotency_key' at all. This leaves the agent without full understanding of all parameters.

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 the action ('Cancel'), the object ('a pending order'), and the identifier ('by ticket'). It distinguishes from sibling tools like 'modify_order' and 'close_position' by specifying the specific operation on a pending order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a behavioral note ('No consent gate (reduces exposure)') that implies when to use this tool over alternatives that may require additional consent. However, it does not explicitly state when not to use or list alternative tools.

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