Skip to main content
Glama

create_order

Create an order from a quote. Returns the order id plus what the user must sign: a deposit address / PSBT for onramps, or the EVM or Tron transaction otherwise.

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

Input Schema

NameRequiredDescriptionDefault
quoteYesThe quote object exactly as returned by `get_quote`, e.g. {"onramp": {...}}; not a string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the mutation profile is known. The description goes further by disclosing the return payload — an order id plus the signing artifact (deposit address/PSBT for onramps, EVM or Tron transaction otherwise), which is meaningful because there is no output schema. It stops short of stating idempotency, quote-expiry failure behavior, or the expected follow-up call.

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?

Two tight sentences: the action first, then the return contract. Every clause earns its place, including the onramp-vs-EVM/Tron branch, which is genuinely needed information rather than padding.

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?

With no output schema and a nested-object parameter, the description correctly spends its budget explaining the return value, which is the main gap structured data leaves. It is slightly incomplete on sequencing — nothing tells the agent to poll wait_for_order or submit via register_tx afterward, and no failure modes are described.

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 description coverage is 100% and the single parameter is well documented, including the warning not to pass a string, so the schema carries the load. The description only echoes 'from a quote' without adding format or validation detail beyond it, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Create an order') and adds the source constraint ('from a quote'), which distinguishes it from a quote-then-create flow. It does not explicitly name quote_and_create as the alternative, but the input requirement makes the distinction inferable.

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?

The only usage hint is implicit: an order is built 'from a quote', and the schema reinforces this by pointing at get_quote's output. There is no explicit when-to-use/when-not statement, no mention of quote_and_create as the combined alternative, and no note on quote expiry or reuse.

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