DoubleData MCP

Cancel ISP renewal

isp_cancel_renewal

DestructiveIdempotent

Cancel an ISP subscription's automatic renewal; proxies remain active until the current billing period ends. Confirm with matching subscription IDs to stop future charges.

Instructions

Stop an ISP subscription from renewing. Proxies keep working until the current period ends. Set confirm_subscription_id to the same ID to proceed.

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": {
      "subscription_id": "<subscription_id>",
      "confirm_subscription_id": "<confirm_subscription_id>"
    },
    "name": "isp_cancel_renewal"
  }
}

Input Schema

Name	Required	Description	Default
`subscription_id`	Yes
`confirm_subscription_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: proxies keep working until the current period ends, and the call requires a matching confirm_subscription_id. It does not say whether the cancellation can be undone, which is the main remaining gap.

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?

Three short sentences, zero waste, with the core action front-loaded and the side effect and confirmation requirement following in priority order.

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 two-parameter destructive mutation with no output schema, the description covers the action, the post-cancellation state of proxies, and the confirmation mechanism. Only reversibility and the response shape are unaddressed, which is a minor gap given the annotations already flag destructiveness.

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?

Schema description coverage is 0%, so the description must carry the load, and it does for the critical parameter: confirm_subscription_id must be set to the same ID as subscription_id, which is a guard-rail the schema does not convey. subscription_id itself is left implicit, but its meaning is evident from the tool purpose.

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 and resource: 'Stop an ISP subscription from renewing.' An agent can distinguish this from isp_subscriptions (listing) or isp_order (purchasing) without opening the schema, though no sibling is named 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 by the purpose (use it to prevent renewal), and the confirmation requirement is spelled out. However, there is no explicit when-not guidance, no mention of how to reverse a cancellation, and no pointer to alternatives such as isp_subscriptions for inspecting the subscription first.

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