Skip to main content
Glama

accept_delivery

Buyer: "I accept this work." Seals the order: the acceptance is signed and anchored in Bitcoin and Stellar with the receipt, counts for the seller's Word Pass, and the order can no longer be disputed. Without it a delivery counts as accepted 14 days after it arrived. Needs your key.

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
api_keyNoyour key, if your client cannot send headers
order_idYesOrder id from buy or my_orders, e.g. "or_…".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "your key, if your client cannot send headers",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / order_id / description
      Added value: +"Order id from buy or my_orders, e.g. \"or_…\"."
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes much further by disclosing irreversibility ('the order can no longer be disputed'), the signing and anchoring in Bitcoin and Stellar, the Word Pass consequence, and the authentication requirement ('Needs your key'). It does not say what happens on a repeated call, even though idempotentHint=false, which is the one remaining gap 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?

Three tight sentences are front-loaded with the action and its consequences; nothing is wasted. Some phrasing is marketing-flavoured ('Seals the order', 'Word Pass'), which costs a little clarity for an agent that has no prior domain context.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with annotations and no output schema, the description covers the actor, the effect, the irreversibility, the authentication requirement, and the default path if the tool is not called; that is everything needed to decide and invoke it.

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?

Schema coverage is 100%, so the baseline is 3. The line 'Needs your key' nevertheless adds meaning beyond the schema, because the api_key field is documented as an optional header fallback, while this operation is in fact authenticated; the description also identifies the actor as the buyer, which frames the meaning of order_id.

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?

The description states a concrete action (the buyer accepting delivered work) and its immediate effect: the acceptance is signed, anchored in Bitcoin and Stellar with the receipt, and the order is sealed. That is far more specific than the tool name alone, and the effect 'the order can no longer be disputed' tells an agent exactly what this call accomplishes compared with read-only siblings such as get_order or verify_receipt.

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?

It makes clear this is the buyer's confirmation step and gives the fallback: without it, a delivery counts as accepted 14 days after it arrives, which is effectively a when-not-to-use / default-path signal. It does not name an alternative sibling for partially rejecting or disputing a delivery, so the guidance is strong but not exhaustive.

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