Skip to main content
Glama

Moqway

Confirm receipt

confirm_receipt
Destructive

Confirms the shipment arrived. Starts a 7-day window for disputes, after which funds are released to the supplier. Only call this when the buyer confirms delivery. Afterwards, ask the buyer how the goods were and record it with rate_order.

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>"
    },
    "name": "confirm_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only flag destructive=true and idempotent=false; the description supplies the concrete consequence that the annotations cannot: a 7-day dispute window opens and funds are then released to the supplier, making the irreversibility tangible. This is exactly the context an agent needs before invoking an irreversible mutation.

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?

Three short sentences ordered purpose, consequence, precondition, follow-up. Every sentence earns its place; only minor tightening would improve it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 description covers the action, the precondition, the downstream consequence, and the next step. It omits what happens on error or if the order was already confirmed (consistent with idempotent=false), which is a small but real gap.

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?

There is one parameter with 0% schema description coverage, so the schema gives name and constraints only. The description implies the identifier refers to the order whose shipment arrived, but never states the format or what an invalid/unknown order_id does, so it only partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('confirms the shipment arrived') and explicitly ties itself to a downstream sibling ('record it with rate_order'), so an agent can separate it from rate_order, cancel_order, and open_dispute without inspecting schemas.

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?

'Only call this when the buyer confirms delivery' gives a clear precondition and implicit exclusion, and the follow-up sentence sequences it before rate_order. It does not mention how this interacts with open_dispute or cancel_order, but the when-to-use condition itself is unambiguous.

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