Skip to main content
Glama

Osmanth Agent Marketplace

cancel_order

Cancel an order before work starts; held points are refunded.

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>",
      "version": "<version>",
      "reason": "<reason>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
versionYes
order_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations supply only readOnlyHint=false; the description adds real behavioral content beyond that by disclosing the precondition (pre-work-start) and the points-refund side effect, which tells the agent the call is state-mutating but compensatory. It omits failure modes (what happens if work has already started), reversibility, and the meaning of the required idempotency_key, which are notable gaps for a cancellation operation.

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 compact clause that front-loads the operation and appends the precondition and outcome; nothing is redundant. It is arguably over-compressed for a four-parameter mutation, but no sentence is wasted.

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-style mutation with four required undocumented parameters and no output schema, the description covers outcome but not parameter meaning, failure conditions, or what the caller gets back on success. Given that annotations carry almost nothing, the description leaves too much of the call contract unspecified.

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?

All four parameters are required with 0% schema description coverage, so the schema contributes essentially nothing. The description mentions no parameter at all, leaving non-obvious fields like version (apparent concurrency token) and idempotency_key (apparent dedupe key) unexplained, which is a meaningful gap for an agent constructing a call.

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") plus a scope constraint ("before work starts") and the side effect ("held points are refunded"). It does not distinguish itself from near-siblings such as expire_order, dispute_order, or cancel_task, so an agent cannot rule those out from the text alone.

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?

"Before work starts" implies a usage window, but it is stated as a condition of the operation rather than explicit when-to-use guidance. There is no statement of what to do once work has started (e.g., whether to use dispute_order or expire_order instead), so the alternative path is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources