Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Reopen order

reopen_order
Destructive

Reopen a closed order to mark it as work in progress again. Use it when an order was closed by mistake; canceled orders cannot be reopened.

Instructions

Reopen a closed order so it shows as work in progress again. A canceled order cannot be reopened.

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

Input Schema

NameRequiredDescriptionDefault
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating, potentially destructive operation. The description adds the meaningful state constraint that canceled orders are ineligible, but does not say what is lost or reset when a closed order is reopened (e.g. fulfillment or completion state), which is the key unknown for a tool flagged destructive.

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, front-loaded with the action and its effect, followed by the single eligibility restriction. Nothing is wasted and nothing is buried.

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 state-change tool with no output schema, the description covers the action and the main precondition. It is thin on what reopening does to the order's existing data and whether any permission is needed, both relevant given the destructive flag.

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 description coverage is 0%, so the single required orderId parameter carries no documentation beyond its name, minLength, and required flag. The name is self-explanatory and the description adds nothing further, so the schema and the obvious naming do just enough to make the call possible.

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 ('Reopen a closed order') plus the resulting state ('shows as work in progress again'), which tells an agent exactly what the tool accomplishes. It does not name or contrast with adjacent siblings (close_order, cancel_order), but the state transition is unambiguous on its own.

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?

Provides a clear precondition (the order must be closed) and an explicit exclusion ('A canceled order cannot be reopened'), which is exactly the kind of guard that prevents a bad call. It stops short of naming an alternative path for canceled orders, leaving the agent to infer one.

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