Skip to main content
Glama
Sign In
@opensmm/mcp-server

@opensmm/mcp-server

Official
by opensmm-protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Cancel an order

cancel_order
DestructiveIdempotent

Cancel an order when the service supports it: unpaid orders cancel immediately; executing orders are canceled at the provider and payment moves to refunding.

Instructions

Cancel an order when the service supports it. Unpaid orders cancel immediately; executing orders are canceled at the provider and the payment moves to REFUNDING.

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

Input Schema

NameRequiredDescriptionDefault
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description goes beyond that by disclosing outcome semantics per state: unpaid orders cancel immediately, while executing orders cancel at the provider and the payment transitions to REFUNDING. It does not describe failure behavior when the service does not support cancellation.

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, the precondition front-loaded and the state-dependent outcomes following. Every clause carries information; nothing is redundant or padded.

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

Completeness3/5

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

For a one-parameter destructive mutation with no output schema, the description covers the main behavioral branch (payment → REFUNDING) but omits how the agent learns the resulting order state, what error surfaces when cancellation is unsupported, and any detail about the orderId argument. Adequate but with clear gaps.

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 orderId parameter (only a regex pattern is given), and the description never mentions the parameter at all. With one parameter that is not zero-parameter baseline, the prose should have explained what identifier is expected and its format, but it adds no meaning beyond the schema.

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 and resource ('Cancel an order') and immediately qualifies the precondition ('when the service supports it'). The action is unmistakable against siblings like create_order or get_order_status, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

'When the service supports it' is the only usage condition given, and it is left vague — the agent is not told how to determine support, nor what to do if cancellation is unavailable. No when-not-to-use guidance is offered, e.g. for orders already refunded or completed.

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