DoubleData MCP

List ISP subscriptions

isp_subscriptions

Read-only

Retrieve active ISP subscription details, including countries, proxy counts, renewal dates, remaining rotations, and IP authorization status for account monitoring.

Instructions

List active ISP subscriptions with countries, proxy count, renewal date, remaining rotations and IP authorization.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "isp_subscriptions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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 readOnlyHint=true and openWorldHint=true, so the description's job is to add context, which it does by disclosing the active-only filter and the exact data returned (countries, proxy count, renewal date, remaining rotations, IP authorization). It does not mention pagination, auth requirements, or ordering, which keeps it short of a 5.

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?

A single front-loaded sentence with the scope constraint first and the returned fields after; no filler or redundant restatement of the title.

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?

With no output schema, the description usefully enumerates the returned fields, and for a zero-parameter read-only list tool that covers most of what an agent needs. The remaining gaps — pagination/result size and whether credentials or a specific account context are required — are minor.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The field list in the description describes output content rather than inputs, which is still useful for callers.

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?

Specific verb ('List') plus resource ('ISP subscriptions') with a scope qualifier ('active') and an enumeration of the fields surfaced. An agent can tell this apart from isp_order, isp_catalog and isp_cancel_renewal, though it never names 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 only implied through the word 'active' — the reader infers cancelled/expired subscriptions are excluded and that this is the read path for existing subscriptions. There is no explicit when-to-use, when-not-to-use, or pointer to isp_catalog/isp_order for other cases.

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