Skip to main content
Glama

accept_delivery

DestructiveIdempotent

Buyer accepts a verified delivery and releases reserved trial credits once. Final settlement; verify result and delegated authority first.

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

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive, idempotent and open-world behavior, and the description adds real context on top: credits are released exactly once, this is final settlement, and delegated authority must be verified beforehand. The 'once' wording is consistent with idempotentHint=true. It does not describe what happens on a failed or already-accepted call.

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 tight sentences with the action and its effect front-loaded, and the precondition placed last as a checklist item. 'Verify result' is slightly telegraphic — it is unclear whether the result to verify is the delivery or the credit release — but nothing is redundant.

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 destructive mutation with no output schema, the description covers the effect, the idempotency guarantee, and the authority precondition. Remaining gaps — preconditions on order state and error behavior — are modest but real for a credits-releasing operation.

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?

With one required parameter at 0% schema description coverage, the description carries the burden and only partially does: it implies order_id refers to a verified, delivered order but never states the required state or format. The link between 'verified delivery' and the order identifier is left for the agent to infer.

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 ('accepts') and resource ('delivery') plus the concrete side effect ('releases reserved trial credits'), which sets it apart from deliver_order and dispute_delivery. It stops short of naming any sibling explicitly, so the differentiation is inferred from 'Final settlement' 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 Guidelines3/5

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

'Final settlement; verify result and delegated authority first' supplies preconditions and implies the tool is terminal, which is genuine when-to-use guidance. However, no alternative path is named — an agent facing a faulty delivery gets no pointer to dispute_delivery or cancel_order, and there are no explicit when-not conditions.

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