Skip to main content
Glama

Confirm delivery

confirm_delivery
DestructiveIdempotent

Releases payment to the driver. Auto-confirms 24h after delivery if you don't.

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": {
      "delivery_id": "<delivery_id>"
    },
    "name": "confirm_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is partly covered. The description adds important context beyond the annotations: confirming releases payment to the driver, and leaving it undone results in an automatic confirmation after 24 hours. It does not address the financial consequences of an early confirmation or what happens if the delivery was already confirmed.

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?

The description is two short sentences. The primary effect (releasing payment) comes first, and the auto-confirm fallback comes second. There is no wasted wording and no missing context.

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, payment-releasing action with no output schema, the description covers the essentials: what it does and the effect of inaction. It would be stronger if it noted whether confirmation is reversible after payment release and what error or state occurs for an already-confirmed delivery.

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 only one parameter, delivery_id, and schema description coverage is 0%, so the description does not clarify its format (for example, an ID prefix or UUID) or how to obtain it. Because there is a single required parameter, this is a minor gap, but it is not the free baseline that a zero-parameter tool would have.

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 uses a concrete verb and names the real effect: 'Releases payment to the driver', which clarifies that confirm_delivery is a financial release action rather than a mere status flag. This meaningfully separates it from siblings like get_delivery, track_delivery, and cancel_delivery, although it never explicitly names those alternatives.

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?

The second sentence provides clear context for when this tool is needed and when it can be omitted: the system auto-confirms 24 hours after delivery if the caller does nothing. That implicit 'only call if you need to release payment before the timeout' guidance is useful. However, it does not explain what conditions would warrant early confirmation or point to a sibling for related steps.

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.