TradeHub

Order request status

get_order_request_status

Read-onlyIdempotent

The current state of an order request made with execute_previewed_order: pending_approval, executed, rejected, failed, expired or declined, with fill price and stop order id once executed. Use to follow an order that was waiting for a person's approval. Not for listing orders (use get_my_open_orders). Input: request_id. Next: get_my_open_positions once executed.

Input Schema

Name	Required	Description	Default
`request_id`	Yes	From execute_previewed_order

Output Schema

Name	Required	Description
`ok`	Yes	False when rejected or failed
`fee`	No	Once executed: the trading fee, estimated at once and replaced by the amount the exchange charged once its fill records show it
`legs`	No	A ladder entry: per leg {price, size_base, order_id, sl_oid, status}; status resting, or after a refused leg withdrawn, filled or partly_filled
`error`	No	Why it was rejected or failed
`venue`	No	Venue name
`checks`	No	Checks run at execution
`sl_oid`	No	Venue order id of the protective stop
`status`	Yes	pending_approval, armed (a trigger entry waiting for its price), executed, rejected, failed, expired, declined, cancelled, or executing (TradeHub has not confirmed the outcome yet: check get_order_request_status)
`receipt`	No	Signed receipt (compact JWS, EdDSA) once executed: request, checks, preview price, fill, slippage, order ids, delegation. Verify with /.well-known/tradehub-receipts.jwks
`order_id`	No	Venue order id of the fill
`fill_price`	No	Average fill, USD per coin
`request_id`	Yes	Order request id; get_order_request_status(request_id) follows it
`deprecation`	No	Present only while this tool is deprecated: replacement, removal_date, changelog
`filled_size`	No	Filled size, in the base coin (e.g. BTC), not USD
`take_profits`	No	set_take_profit_levels: the take-profits now on the exchange
`trigger_price`	No	status armed: opens at market when the mark reaches this, USD per coin
`trigger_expires_at`	No	status armed: when it lapses unless reached, ISO 8601 UTC
`approval_expires_at`	No	While pending: when the approval request lapses, ISO 8601 UTC

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedOutput schema / properties / legs

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "A ladder entry: per leg {price, size_base, order_id, sl_oid, status}; status resting, or after a refused leg withdrawn, filled or partly_filled",
+  "title": "Legs"
+}

Changed2 schema fields changedOct 27, 2026

addedOutput schema / $defs / FeeOut

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "actual": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The charged amount in asset; negative = a rebate",
+      "title": "Actual"
+    },
+    "actual_usd": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "What the exchange charged, USD; null until its fill records show it (or when charged in another asset, see actual and asset)",
+      "title": "Actual Usd"
+    },
+    "asset": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The asset it was charged in (USDT, USDC, BNB …)",
+      "title": "Asset"
+    },
+    "deprecation": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Present only while this tool is deprecated: replacement, removal_date, changelog",
+      "title": "Deprecation"
+    },
+    "estimated_usd": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The account's rate x the filled notional, USD",
+      "title": "Estimated Usd"
+    },
+    "kind": {
+      "description": "open or close",
+      "title": "Kind",
+      "type": "string"
+    },
+    "status": {
+      "description": "pending (not read yet), done, or unknown (the exchange never showed it)",
+      "title": "Status",
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "estimated_usd",
+    "actual_usd",
+    "actual",
+    "asset",
+    "status"
+  ],
+  "title": "FeeOut",
+  "type": "object"
+}

addedOutput schema / properties / fee

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/FeeOut"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Once executed: the trading fee, estimated at once and replaced by the amount the exchange charged once its fill records show it"
+}

First observedOct 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the full state machine (pending_approval, executed, rejected, failed, expired, declined) and what becomes available after execution (fill price, stop order id). It stops short of describing polling behavior or expiry timing, so it is strong but not exhaustive.

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?

Front-loaded with the resource and its states, then usage, exclusion, and next step in a compact sequence. Slightly weakened by the redundant 'Input: request_id' line, which duplicates the required schema field rather than adding information.

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

Completeness5/5

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

With an output schema present, the description need not explain return structure; it supplies the state vocabulary, the trigger condition for use, the exclusion, and the downstream tool. For a single-parameter read-only status check, that is everything an agent needs to call it correctly.

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 100% and the schema already documents request_id as coming 'From execute_previewed_order'. The description's 'Input: request_id' merely restates the field name without adding format or sourcing detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('current state of an order request made with execute_previewed_order') and enumerates the exact state values returned, plus the fields available once executed. It is clearly distinguishable from siblings like execute_previewed_order and get_my_open_orders without opening any schema.

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?

Explicitly gives the when ('use to follow an order that was waiting for a person's approval'), the when-not with a named alternative ('not for listing orders, use get_my_open_orders'), and a follow-up path ('get_my_open_positions once executed'). Nothing about tool selection is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TradeHub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?