ICONIC Agent-Native Marketplace — Seven Specialist Services

Get Order

marketplace_get_order

Read-only

Capability-protected order status and report after separate verified payment.

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": {
      "order_id": "<order_id>",
      "order_access_token": "<order_access_token>"
    },
    "name": "marketplace_get_order"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes
`order_access_token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already establish this as a safe, read-only operation. The description adds useful context that access is capability-protected and intended after separate verified payment, but it does not explain invalid-token behavior, missing-payment errors, or other operational limits.

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?

The definition is a single compact sentence with no wasted wording and front-loads the capability-protection constraint. It is terse, but the brevity is mostly efficient rather than 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?

For a low-complexity read-only getter with no output schema, the description covers the payment precondition and capability protection. However, with two required parameters at 0% schema description coverage, it should do more to explain parameter acquisition and meaning.

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 0%, so the description must carry parameter meaning. It hints that order_access_token is a capability token, but it does not explain order_id format, token source, or how the two parameters relate, leaving significant gaps.

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 states a clear resource and result: order status and report retrieval, with a capability-protection constraint. It does not explicitly distinguish this tool from siblings such as marketplace_get_offer, but the core purpose is understandable.

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 'after separate verified payment' gives an implied usage condition, but the description does not state when not to use this tool or name alternatives. An agent can infer this is a post-payment read operation, but routing guidance is limited.

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

All ICONIC Agent-Native Marketplace — Seven Specialist Services 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?