Skip to main content
Glama

Babelii-Diofis Account

Buat pesanan setelah dikonfirmasi

execute_purchase
DestructiveIdempotent

Place the prepared order only after explicit user confirmation of details and terms. Requires orders.execute scope; identity determines payment authority. Retrying the SAME intent never authorizes another order. Do not replace an indeterminate intent with a new one. Payment: omit pay_with to use the default shown in the prepared summary (payment.default). Pass pay_with (gateway, cash or coin) and, for gateway, channel only when the buyer chose a method that appears in payment.options; a method that is not listed is refused.

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": {
      "intent_id": "<intent_id>"
    },
    "name": "execute_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNo
pay_withNo
confirmedNo
intent_idYes
quote_versionNo
terms_acceptedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the required orders.execute scope, that identity determines payment authority, and the idempotency contract at the intent level (same intent never authorizes a second order; an indeterminate intent must not be replaced). For a destructiveHint=true mutation, that is exactly the context an agent needs beyond readOnly/destructive/idempotent flags.

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?

Front-loaded with the precondition, then scope/identity, then retry safety, then payment parameter rules — a deliberate risk-ordered structure. The final sentence is dense but every clause carries a rule that changes agent behavior; nothing is filler.

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?

An output schema exists, so return values need not be described, and the destructive/idempotent semantics are covered thoroughly. The remaining gap is the confirmed and terms_accepted booleans — the description never says whether they must be true for execution to succeed, which matters for a destructive call with a 0%-documented schema.

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 description coverage is 0%, so the description carries the load and does so for the risky parameters: pay_with values (gateway, cash, coin) that are not enumerated in the schema, the channel's gateway-only applicability, the default-payment omission rule, and intent_id's retry semantics. It leaves quote_version, confirmed and terms_accepted unexplained — the confirmation flags are only obliquely implied — which keeps it from a 5.

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 ('Place the prepared order') and scopes it to a post-confirmation step, which clearly positions it downstream of prepare_purchase and apart from inquire_purchase/purchase_status. It does not name a sibling explicitly, so it stops short of full differentiation, but the 'prepared order' framing makes the pipeline position unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit when-to-use ('only after explicit user confirmation of details and terms'), explicit when-not (a method that appears in payment.options is required for pay_with; unlisted methods are refused), and explicit retry guidance ('Retrying the SAME intent never authorizes another order', 'Do not replace an indeterminate intent with a new one'). An agent has no ambiguity about whether to call or retry.

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