DoubleData MCP

ISP order status

isp_order_status

Read-only

Check an ISP order's provisioning progress and retrieve the resulting subscription details by order ID.

Instructions

Check an ISP order's provisioning status and the resulting subscription.

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

Input Schema

Name	Required	Description	Default
`order_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by noting the response includes the resulting subscription, but it omits behavior an agent would want: what happens for an unknown or still-pending order, and whether the status is live or cached.

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?

One short, front-loaded sentence with no filler. It could be slightly stronger by naming the outcome ordering (status first, then subscription) more explicitly, but there is no waste.

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?

For a simple single-parameter read tool whose safety profile is carried by annotations, this is close to sufficient. However, with no output schema, the description should say more about the returned status values and the not-found case than the single clause it provides.

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?

The single parameter has 0% schema description coverage, so only its name and UUID format are documented. The description's phrase "an ISP order's provisioning status" lightly implies that order_id is the ISP order identifier rather than a subscription ID, but it does not confirm that or state where the ID comes from.

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 gives a specific verb and resource ("Check an ISP order's provisioning status") plus a second outcome ("the resulting subscription"), which cleanly separates it from isp_order and isp_rotation_status. It is clear without needing to name a sibling explicitly.

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 rather than stated: an agent can infer this is the polling/lookup step after an ISP order, but the description never says when to call it versus isp_order, isp_subscriptions, or isp_rotation_status, nor whether repeated polling is expected.

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