Skip to main content
Glama

deliver_commerce_order

deliver_commerce_order

Seller: record delivery proof for an 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>",
      "deliveryHash": "<deliveryHash>"
    },
    "name": "deliver_commerce_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesOrder id.
deliveryUriNoOptional delivery location.
deliveryHashYessha256 hash or 0x hash of the delivery.
deliverySignatureNoOptional seller signature over the delivery proof.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, and it discloses only one behavior: authentication is required. It says nothing about whether the call mutates order state, whether it is idempotent, what happens if a delivery proof already exists, or whether the hash is verified on-chain — all critical for an unrecoverable proof-recording 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?

Two short sentences, no filler, with the actor and action front-loaded. It is not padded, though the extreme terseness leaves little room for the behavioral context an unannotated mutation tool needs.

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 four-parameter state-mutating proof-recording tool with no annotations and no output schema, the description is under-specified: an agent cannot tell what the call changes, what a success or failure looks like, or how it fits with complete_commerce_order.

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 100%, so every parameter including deliveryHash and deliverySignature is already documented in the schema. The description adds no format, constraint, or relationship detail (e.g. whether deliveryUri and deliverySignature must correspond to deliveryHash), so the baseline 3 applies.

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?

The description gives a specific verb and resource: 'record delivery proof for an order', plus the actor role ('Seller'). This is meaningfully clearer than the bare title, though it never contrasts itself with the lifecycle sibling complete_commerce_order, so the boundary is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus complete_commerce_order or accept/create quote tools, no preconditions (e.g. order must be in a delivered-pending state), and no when-not-to-use note. The 'Seller:' prefix hints at who calls it but not when.

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