Skip to main content
Glama

Create order

create_order

Buy a bounded model question or review. Consult get_offers for current models, limits and payment rails. Requires scope 'orders:write'.

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": {
      "question": "<question>",
      "client_order_key": "<client_order_key>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNogeneral
railNostripe_test
offerNoAn offer id from GET /v1/offers (second opinions) or model_offers (quick_answer_v2, structured_review_v2, compare_2_v2, compare_3_v2).second_opinion_1
modelsNoModel offers only: the exact model(s) to run, from the offer's list. Defaults to the offer's default models. Never substituted.
contextNoSupporting material: logs, code, error text. Max 48 KiB.
questionYesWhat to review. Max 16 KiB.
idempotency_keyNoOptional. Same key + same arguments within 24 h returns the original result.
proposed_answerNoThe agent's current answer or plan, if any. Max 32 KiB.
authorization_idNoDefaults to the newest matching authorization.
client_order_keyYesYour unique key for this purchase. Retrying with the same key and body returns the same order and never charges twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / offer / description
      Previous value: -"An offer id from GET /v1/offers (second opinions) or model_offers (quick_answer_v1, structured_review_v1, compare_2_v1, compare_3_v1)."New value: +"An offer id from GET /v1/offers (second opinions) or model_offers (quick_answer_v2, structured_review_v2, compare_2_v2, compare_3_v2)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description adds the authorization scope required and the prerequisite discovery step via get_offers, both of which the agent needs before calling. The charging behavior is covered in the schema's client_order_key description rather than here; note the slight tension with idempotentHint=false, though per-call idempotency is genuinely key-dependent, so this is not a true contradiction.

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?

Three short sentences, front-loaded with the action, then the discovery route, then the permission gate. No filler and nothing repeated from structured fields verbatim.

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

Completeness3/5

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

For a 10-parameter financial mutation with no output schema, the description says nothing about what is returned (order id, status, whether the call blocks until the review completes) or how authorization_id and credit vs stripe rails interact. The schema carries most of the load, but the return contract remains unspecified.

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 already 80%, so the baseline is 3. The description adds routing meaning by tying offers, models and rails to get_offers as the source of valid values, which clarifies the enum/string parameters beyond their raw schema text.

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 ('Buy a bounded model question or review'), which tells the agent this creates a paid order rather than merely fetching one. It implicitly distinguishes itself from get_offers/get_order by pointing to get_offers for catalog data, though the phrasing 'bounded model question' is somewhat jargon-heavy.

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?

Explicitly directs the agent to consult get_offers first for models, limits and payment rails, and states the required scope 'orders:write'. It does not address when to prefer create_credit_purchase or create_spending_authorization instead, leaving some routing to inference.

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