@ethioviral/mcp

Get order status

get_order

Retrieve the current status of a specific order by its ID to confirm updates after placing an order or recover from a timed-out request.

Instructions

Fetches the current status of one order by id — use this to re-check an order after create_order, or to recover from a timed-out call.

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

Input Schema

Name	Required	Description	Default
`orderId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. The verb 'Fetches' clearly signals a read-only operation, and the timeout-recovery use case implies the tool is safe to call again after uncertainty. It does not describe error behavior or response shape, but for a simple getter the key safety trait is clear.

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?

The description is a single front-loaded sentence that states the core operation first and then gives two concrete use cases. Every word earns its place with no repetition or filler.

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 one-parameter tool with no output schema, the description covers what the tool does, what it operates on, and when to use it. It does not enumerate possible status values or explicitly route away from premium/SMM siblings, but the create_order reference provides enough orientation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides only the parameter name and type for orderId, so the description adds meaning by explaining that the parameter is the ID of the order to check and that it is likely obtained from create_order. This meaningfully compensates for the 0% schema description coverage.

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 uses a specific verb and resource: it fetches the current status of one order by id, which clearly distinguishes this from list/history tools and from SMM/premium order variants. The purpose is immediately clear to an agent.

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?

It explicitly states when to use the tool: to re-check an order after create_order or to recover from a timed-out call. It does not provide exclusions or name alternative tools such as get_smm_order or get_premium_order, so it stops short of a 5.

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