Skip to main content
Glama

pay_order_part

Pay one part of an artwork order via x402 (amount and recipient come from the order). When all parts are paid, the area is yours.

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

Input Schema

NameRequiredDescriptionDefault
partYes
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that payment runs over x402 and that amount and recipient are derived from the order rather than supplied by the caller, plus the end effect ('the area is yours'). It omits whether payment is irreversible, whether calls are idempotent, what happens on partial failure, and any wallet/auth requirements.

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, front-loaded with the action and protocol, then the payoff condition. 'The area is yours' is slightly promotional but does convey the ownership outcome, so little is wasted.

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?

This is a payment/mutation tool with no annotations, no output schema, and 0% parameter description coverage — the highest-burden combination. Missing auth/wallet expectations, failure and retry semantics, and the meaning of the 'part' index leave an agent under-informed before spending funds.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain both parameters. It clarifies order_id indirectly by saying amount and recipient come from the order, but 'part' is never defined beyond the phrase 'one part' — the 1–6 range, ordering rules, and whether a part can be paid twice are left entirely unexplained.

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?

States a specific verb and resource ('Pay one part of an artwork order via x402') and makes the partial-payment model explicit. It does not name or distinguish itself from siblings like create_artwork_order or buy_pixel, but the 'part of an order' scope is distinctive enough to separate it from a direct pixel purchase.

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?

Usage is implied rather than stated: an agent can infer this is called repeatedly, once per part, against an existing order. There is no explicit prerequisite (e.g., that order_id comes from create_artwork_order), no guidance on whether parts must be paid in sequence, and no stated alternative for full-payment or direct-purchase flows.

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.