Mercadopleis

get_delivery

Get the on-chain SHA-256 commitment of a delivered order so the buyer can verify the deliverable: the hash of the uploaded file, or of the link text when the seller delivered an external link.

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_delivery"
  }
}

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

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does useful work by explaining exactly what the returned hash covers (uploaded file bytes vs link text) and implying the order must be 'delivered'. It omits prerequisites (permissions, wallet context), failure behavior for undelivered or unknown orders, and the return type/format.

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 front-loaded sentence with no filler; the colon clause adds real information about hash derivation rather than padding.

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?

For a 3-parameter tool with no output schema and no annotations, the description adequately explains the returned value's semantics but leaves chainId unexplained and gives no precondition or error context, so it is only just sufficient.

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% – chainId and orderId are undocumented in both schema and description. The description mentions 'order' generically but adds no meaning about chainId or escrowVersion selection beyond what the schema already says.

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 ('Get') and a precise resource ('on-chain SHA-256 commitment of a delivered order'), which is materially different from sibling get_deliverable, though it never names that sibling to make the contrast explicit.

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 phrase 'so the buyer can verify the deliverable' implies the verification use case, but there is no explicit when-to-use vs when-not guidance and no named alternative for fetching the actual deliverable content.

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.