Skip to main content
Glama

Name order status

get_name_order
Read-onlyIdempotent

Use after buy_name to follow your order until the name is delivered. Free. Status of a vanity name order: awaiting_payment, payment_seen, paid, registering, transferring, delivered (or expired, cancelled, needs_review, refunded), with the payment, register and transfer tx ids. Polling also moves a paid order forward. Read-only for the caller.

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

Input Schema

NameRequiredDescriptionDefault
order_idYesorder_id from buy_name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses cost ('Free'), the full status vocabulary including terminal failure states, that payment/register/transfer tx ids are returned, and the non-obvious trait that polling itself advances a paid order. 'Read-only for the caller' is consistent with readOnlyHint=true, so there is no contradiction.

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 usage cue is front-loaded and the status enumeration earns its space by telling the agent what values to expect. The telegraphic, comma-spliced phrasing of the tx-id clause is slightly compressed but not wasteful.

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?

With no output schema, the description compensates by listing the statuses and the transaction ids returned, and it flags the polling side effect. For a single-parameter status tool with annotations covering the safety profile, nothing needed to call it correctly is missing.

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?

There is one parameter at 100% schema coverage, and the schema already documents order_id with its hex pattern and provenance. The description mentions order ids only as return values, adding no new meaning about the input beyond the schema, so the baseline of 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 resource ('vanity name order') and its status, and positions the tool in a workflow after buy_name. That distinguishes it clearly from buy_name (create) and cancel_name_order (mutate), so an agent can select it without inspecting schemas.

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?

'Use after buy_name to follow your order until the name is delivered' gives explicit lifecycle context and sequencing. It does not say what to do instead for cancelling or re-quoting, so it stops short of naming alternatives or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.