HiddenSwap

Check an order

get_order_status

Read-onlyIdempotent

Check the stage of a HiddenSwap order by its order ID, for example awaiting deposit, confirming, swapping, sending, complete, needs support, refunded or expired. The order ID is private: anyone who has it can open the order page, which shows the addresses and amounts unless the owner hid the order. Only use an order ID the person gave you, and never repeat it anywhere else. Returns the stage, a short label, whether it is final, when it last changed, and links to the order page and support. It never returns addresses, amounts or transaction hashes. For a hidden order, it says only that the order is hidden. Read-only. No account, no email and no ID needed to swap.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`orderId`	Yes	The order ID the person saved when they started the swap. Private: only use one the person gave you.

Output Schema

TableJSON Schema

Name	Required	Description
`final`	Yes
`label`	Yes
`notes`	Yes
`stage`	Yes
`orderId`	Yes
`orderUrl`	Yes
`updatedAt`	Yes	When the stage last changed (ISO 8601).
`supportUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedOutput schema / properties / stage / enum

Previous value: -[
-  "awaiting",
-  "confirming",
-  "exchanging",
-  "sending",
-  "sent",
-  "held",
-  "failed",
-  "refunded",
-  "expired"
-]New value: +[
+  "awaiting",
+  "confirming",
+  "exchanging",
+  "sending",
+  "sent",
+  "failed",
+  "refunded",
+  "expired"
+]

First observedSep 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial disclosure beyond them: the privacy model of the order ID (anyone with it can open the order page showing addresses and amounts unless the order was hidden), what is never returned (addresses, amounts, transaction hashes), and the special hidden-order behavior. That is rich, non-obvious behavioral context.

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 purpose and the stage list, then privacy, then return summary. It is a little long and the trailing 'Read-only. No account, no email and no ID needed to swap.' partly restates the annotations, but every other sentence carries real 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?

Despite an output schema existing (so return values need not be described), the description covers privacy, scope, side effects and return semantics fully. An agent has everything needed to call this correctly and safely.

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% for the single parameter, so the schema already documents its format and private nature. The description reinforces the privacy constraint but adds no syntax, format or validation detail beyond what the schema provides; 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?

The description names a specific verb ('Check') and resource ('HiddenSwap order'), then enumerates the exact stages the tool can return. This is unmistakably distinct from the sibling tools get_pair_info, get_quote and search_coins, which deal with coins, pairs and quotes, not orders.

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?

It gives clear contextual constraints: only use an order ID the person gave you, never repeat it elsewhere, and no account/email/ID is needed. It stops short of explicitly naming an alternative tool or a when-not-to-use condition, but the usage context is unambiguous.

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

All HiddenSwap 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.