Skip to main content
Glama

dynadot_get_order_status

Retrieve the current status of a specific Dynadot order by orderId to check processing progress or completion.

Instructions

Get the status of a specific order.

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": "dynadot_get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • removedInput schema / properties / orderId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "string"
      -  }
      -]
    • addedInput schema / properties / orderId / type
      Added value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv2.0.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description bears full behavioral burden and delivers almost nothing. It does not say whether this is read-only (implied but unstated), what status values are possible, whether status is real-time or eventually consistent, or whether the call requires account ownership of the order.

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

Conciseness3/5

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

One short, front-loaded sentence with zero filler, which is structurally clean. However, the brevity reflects under-specification rather than disciplined concision — the sentence could have carried a return-value note or an ID-format hint at minimal cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one param, no output schema), so a description was needed to explain the shape of the returned status and the meaning of the identifier. Neither is present, and with no output schema the agent has no idea what a successful response looks like.

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 coverage is 0% for the single required parameter, and the description adds nothing about it. It does not clarify whether orderId is numeric or a string identifier, where the caller obtains it (e.g. from dynadot_order_list), or whether both forms are interchangeable.

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?

States a clear verb+resource pair ('Get the status of a specific order'), which is enough to distinguish it from order-listing tools like dynadot_order_list. It does not explicitly differentiate itself from the other status tools in the sibling set (e.g. dynadot_get_transfer_status, dynadot_get_cn_audit_status), leaving the agent to infer that 'order' is a distinct entity type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus the transfer/audit status tools, no prerequisites such as authentication or order-age requirements, and no note on what to do if the order is unknown. The agent must infer all routing decisions from the title alone.

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

Deploy Server

Other Tools