Skip to main content
Glama

create_order

Idempotent

Reserve trial credits for a service. Act only within delegated budget. Use the SAME idempotency_key and exact parameters on retries. Inspect delivery before accept_delivery. Requires bearer authentication.

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": {
      "listing_id": "<listing_id>",
      "input": "<input>",
      "max_price": "<max_price>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesJSON service input; shared with the seller
max_priceYes
listing_idYes
idempotency_keyYesUnique stable key for this purchase, reused unchanged for retries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare openWorldHint, idempotentHint and non-destructive; the description adds material context by stating bearer authentication is required and that spending must stay within delegated budget. However, it never clarifies whether credits are charged immediately or only held, nor what happens to the reservation on failure or timeout, which matters for a credit-consuming mutation.

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?

Four short imperative sentences, no filler, with the core purpose front-loaded. The telegraphic style is efficient, though "Act only within delegated budget" reads as a dangling instruction without stating the consequence of exceeding it.

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 4-parameter, all-required spend operation with no output schema, the description covers authentication, budget constraints, retry semantics and the correct next step in the workflow. The remaining gap is the semantics of max_price and the reservation lifecycle, but overall it is close to self-sufficient.

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?

Schema coverage is only 50%, and the description adds meaning mainly for idempotency_key (stable across retries), which the schema already states. max_price is left unexplained (per-unit cap? total cap?) and listing_id's role in selecting the seller is not described, so the description does not fully compensate for the coverage gap.

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?

"Reserve trial credits for a service" gives a concrete verb and effect (creating an order that holds credits), which is more informative than the bare name create_order. It does not explicitly contrast with siblings like post_request or cancel_order, but naming accept_delivery as the downstream step helps place it in the flow.

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?

Tells the agent to act only within delegated budget, to reuse the same idempotency_key and exact parameters on retries, and to inspect delivery before calling accept_delivery. That is clear usage and sequencing guidance, though it never states when NOT to use this tool (e.g., versus post_request for non-credit requests).

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