audit.domains - Domain Valuation

Check an order

get_order_status

Idempotent

Return an order's state and the next actions open to the token's holder, buyer or seller. Not read-only: each call runs a rate-limited check of the domain move and, when the terms are met, may release the payment to the seller. That is the order proceeding, not an extra charge. Poll no faster than pollAfterSeconds. Use act_on_order instead to confirm, dispute or refund; this tool only reports state and triggers the check.

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

Input Schema

Name	Required	Description	Default
`token`	Yes	The buyer token from checkout, or the seller's manage token. Treat as a secret.
`orderId`	Yes	The order identifier from checkout.

Output Schema

Name	Required	Description
`done`	Yes	True when nothing more is owed.
`role`	Yes
`order`	Yes
`nextActions`	Yes
`pollAfterSeconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026
RemovedOct 6, 2026
First observedSep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Well beyond the annotations: it discloses the rate-limited domain-move check, the side effect of releasing payment when terms are met, and preempts a likely misinterpretation ('That is the order proceeding, not an extra charge'). With readOnlyHint=false and idempotentHint=true already supplied, this is strong added context, though the payment-release disclosure could state more precisely what preconditions trigger it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences, each doing distinct work: capability, side effect, frequency cap, alternative tool. The rate and side-effect warnings are front-loaded where an agent will read them before acting.

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?

An output schema exists, so return values need not be described, and the description covers the non-obvious risks (mutation via payment release, polling limits, sibling routing). The only small gap is the exact conditions under which payment is released, which an agent may want to convey to a user.

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% and both parameters (token, orderId) are documented there, so the schema carries the load. The description reinforces the dual buyer/seller token role but adds no syntax or formatting detail beyond it; pollAfterSeconds appears in the description yet is not an input parameter, so it refers to output and adds no input-side semantics.

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 — returning an order's state and the actions open to the token holder — and names the boundary against the sibling it is not (act_on_order) in the same breath. An agent can separate it from act_on_order, appraisal_order_status, and appraisal_purchase_status 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?

Explicit routing: 'Use act_on_order instead to confirm, dispute or refund' with the exclusion spelled out ('this tool only reports state and triggers the check'). It also gives an operational constraint on call frequency ('poll no faster than pollAfterSeconds'), covering both when-to-use and how-often.

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

All audit.domains - Domain Valuation 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?