Skip to main content
Glama

get_order

Read-only

Get an order's status and details.

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": {
      "id": "<id>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrder id, source Bitcoin txid, or source EVM tx hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety posture is covered. The description adds that the response carries status and details, which is meaningful given there is no output schema, but it omits behavior for unknown/failed ids and whether polling is expected.

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?

A single short sentence with zero filler, and the resource is front-loaded. It is lean to the point of thinness, but nothing is redundant or bloated.

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?

With no output schema, the phrase 'status and details' is the only hint about return values and it stays vague. For a lookup tool in a catalog containing get_orders and wait_for_order, the definition should say enough to route correctly, which it only partially does.

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 100% and the schema already explains that id accepts an order id, source Bitcoin txid, or EVM tx hash, so the description need not repeat it. It adds no extra parameter meaning, but baseline for a fully documented single parameter is met.

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: retrieves an order's status and details. That is clearly distinguishable from write siblings like create_order, but the description never contrasts itself with get_orders or wait_for_order, so the agent must guess which read path applies.

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

Usage Guidelines2/5

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

No when-to-use guidance at all: nothing says to use this for a single known id versus listing via get_orders, and nothing says whether to pair it with wait_for_order for pending orders. The only implicit signal is the singular resource name.

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