Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Close order

close_order
Destructive

Marks an order as done by setting it to closed. Paid and fulfilled orders normally close on their own and reopen if they later stop meeting those conditions.

Instructions

Mark an order done (state closed). Paid and fulfilled orders usually close by themselves; it reopens by itself if it later stops being paid or fulfilled.

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": "close_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the destructiveHint=true annotation, the description discloses two important traits: the order may already have closed automatically, and the closure self-reverts if payment/fulfillment lapses. That reversibility context meaningfully softens how an agent should read the destructive flag. It does not cover permissions or what happens if the order is already closed.

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?

Two compact sentences with the action stated first and the caveat second; nothing is padded. The pronoun-heavy phrasing ("it reopens by itself") is slightly loose but still clear.

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 single-parameter mutation with no output schema, the definition covers what changes and that the change is self-reverting, which is the core need. It omits error/edge behavior such as calling it on an already-closed or unpaid order, which would matter for correct invocation.

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

Parameters3/5

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

Schema coverage is 0%, but there is only one parameter and its name (orderId) is self-explanatory and marked required with a minLength constraint. The description adds no meaning about which order identifier format is expected, so the schema alone carries the load.

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?

"Mark an order done (state closed)" gives a specific verb plus the resulting resource state, which is more precise than the bare tool name. It does not explicitly distinguish itself from cancel_order or reopen_order, so sibling differentiation is left implicit.

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?

Saying paid and fulfilled orders usually close by themselves implies this tool is for orders that don't auto-close, which is useful when-to-use context. However, no alternative is named and there is no explicit when-not guidance (e.g. use cancel_order instead when the order should be voided).

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