Skip to main content
Glama

HokuHost Domains

get_order

Read-only

Order status, payment confirmation (paid_at, receipt_url). Use wait=25 instead of polling.

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

Input Schema

NameRequiredDescriptionDefault
waitNoSeconds to wait for payment/registration to finish (max 25)
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description is not responsible for the safety profile. It adds valuable behavior beyond the annotations: the tool can block for up to 25 seconds waiting for payment or registration, and it returns payment-related fields. It does not disclose what happens if the wait times out or whether an error is raised, which keeps it from a 5.

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 description is short and front-loaded with the retained data, followed by the wait/polling instruction. The telegraphic noun phrase lacks a verb, which slightly reduces clarity, but every sentence carries useful information and there is no waste.

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?

For a simple read-only lookup with one required ID, the description covers what is returned, the long-poll wait behavior, and the anti-polling guidance. Since no output schema exists, not describing the full return shape is a minor gap, but it is otherwise complete enough to call correctly.

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 coverage is 50%: wait is documented in the schema, while order_id is undocumented. The description adds meaning to wait by advising wait=25 instead of polling, but it does not explain order_id semantics. The baseline of 3 is appropriate given partial schema coverage and modest description compensation.

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 identifies the resource (order) and the specific information retrieved (status, payment confirmation with paid_at and receipt_url). It is a noun phrase rather than a clear verb, and it does not explicitly distinguish itself from siblings like list_orders, but an agent can understand its purpose.

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?

It gives one useful usage instruction: use wait=25 instead of polling, which guides the agent away from a polling pattern. However, it lacks guidance on when to choose get_order versus list_orders or other alternatives, and it does not specify exclusions or prerequisites.

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.

Resources