Mercadopleis

get_order_status

Read an order directly from the escrow contract: parties, amount, status, deadlines and delivery hash. On escrow v3 the deadlines are the effective ones (they stop counting while the contract is paused) and a disputed order shows when anyone can close it by timeout. Orders from the old v2 escrow are read with escrowVersion 2.

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": {
      "orderId": "<orderId>"
    },
    "name": "get_order_status"
  }
}

Input Schema

Name	Required	Description
`chainId`	No
`orderId`	Yes
`escrowVersion`	No	Escrow version the order lives in. Default: the current one. Use 2 for orders created before v3.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / escrowVersion

Added value: +{
+  "description": "Escrow version the order lives in. Default: the current one. Use 2 for orders created before v3.",
+  "enum": [
+    2,
+    3
+  ],
+  "type": "number"
+}

First observedOct 20, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares a read-only operation and explains semantics beyond the schema — v3 deadlines pause while the contract is paused, and disputed orders expose a timeout closure path. It still omits failure behavior (order not found, wrong escrowVersion) and any auth/permission 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?

Three tight sentences, front-loaded with the core action and return payload, then version semantics. The final sentence on v2 orders partially duplicates the schema's escrowVersion description but is short enough to earn its place as routing help.

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 no annotations, the description compensates by enumerating the returned fields and explaining v3 deadline/dispute behavior, which is the information an agent needs to interpret results. Gaps remain on the two undocumented parameters and on error/edge-case behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: orderId and chainId have no descriptions in the schema, and the description says nothing about either — it never explains whether chainId defaults to a specific chain or what the order ID space is. The one clarification offered (escrowVersion 2 for pre-v3 orders) largely restates the schema's own parameter description.

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 uses a specific verb ('Read') and a specific resource ('an order directly from the escrow contract'), then enumerates the returned fields (parties, amount, status, deadlines, delivery hash), which makes it clearly distinct from siblings like get_delivery or get_deliverable. It never names a sibling to route against, keeping it just short of a 5.

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?

Guidance is implied rather than stated: the agent learns that old v2 orders need escrowVersion 2, but there is no explicit statement of when to call this tool versus get_delivery/get_deliverable, nor of prerequisites such as authentication or a known orderId.

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

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