Skip to main content
Glama

Outil.io

Get domain order

get_domain_order
Read-only

Suivre une commande de domaine : awaiting_payment (checkoutUrl à ouvrir), paid, configuring, active, failed (remboursé si refunded), cancelled, expired. La lecture fait avancer la commande.

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": {
      "id": "<id>"
    },
    "name": "get_domain_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior1/5

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

'La lecture fait avancer la commande' declares that this call mutates the order's state, while annotations declare readOnlyHint=true and destructiveHint=false. That is a direct conflict between the stated behavior and the structured safety profile, so the agent cannot trust the annotation when deciding whether the call is safe to repeat or poll. The disclosure itself is valuable, but under the scoring rule a description that contradicts annotations scores 1.

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?

Two dense clauses, front-loaded with the lifecycle states and ending with the critical side-effect warning. Nothing is redundant, though the telegraphic French phrasing and parenthetical asides make it slightly harder to parse than a clean sentence would.

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

Completeness3/5

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

There is no output schema, and the description only hints at the return value via 'checkoutUrl à ouvrir'; it does not say what else comes back (status field, domain, timestamps) or how the states map to next actions. It does disclose the non-obvious state-advancement behavior, which is the most important gap filled, but the return contract remains underspecified.

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?

The schema has one required parameter ('id') with 0% description coverage, and the description never mentions it — no statement of whether it is an order ID, a domain name, or a checkout token. With a single opaque identifier the schema alone leaves real ambiguity, and the description does nothing to compensate.

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 specific verb+resource: tracking a domain order, and enumerates the lifecycle states (awaiting_payment, paid, configuring, active, failed, cancelled, expired) plus what checkoutUrl means. It is clear what the tool does, but it never names or distinguishes itself from the sibling get_domain_status, so an agent must guess which of the two to call.

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?

Usage is implied by the state list and by 'checkoutUrl à ouvrir', which suggests calling it after checkout to follow progress. There is no explicit when-to-use versus when-not guidance and no mention of the obvious alternative (get_domain_status), so the selection logic is left to inference.

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.