Skip to main content
Glama

complete_commerce_order

complete_commerce_order

Buyer: confirm a paid, delivered order. Requires authentication.

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

Input Schema

NameRequiredDescriptionDefault
orderIdYesOrder id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose two real traits: it requires authentication and it should only be invoked on an already paid and delivered order. It does not say whether the confirmation is irreversible, what state change occurs, or what happens on a failed confirmation, which are meaningful gaps for a mutation tool.

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 short sentences with the role and preconditions front-loaded and no filler. The 'Buyer:' label is compact but slightly cryptic as to whether it denotes the calling party or the affected party.

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 annotations and no output schema, the description covers the auth requirement and the preconditions, which is the core of what an agent needs. It leaves out the effect of the call, reversibility, and failure behavior, so it is adequate rather than complete.

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

Parameters4/5

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

Only one parameter exists and the schema documents it at 100% coverage ('Order id.'), so the schema already does the work. The description adds no format, sourcing, or validation detail beyond that, but the baseline for a fully covered single-param schema is a 4.

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?

Names a specific verb ('confirm') and resource ('order') and adds the buyer role plus the precondition state ('paid, delivered'), which separates it from the delivery step handled by deliver_commerce_order. It stops short of explicitly contrasting with any sibling, so it is clear but not fully differentiated.

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?

The stated preconditions (order is paid and delivered) implicitly tell the agent when this call is valid, which is useful gating. There is no explicit when-not guidance, no mention of what to do if the order is unpaid or undelivered, and no named alternative such as check_payment_status for verifying the precondition.

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