DoubleData MCP

List ISP proxies

isp_proxies

Read-only

List the static IPs tied to an ISP subscription, with passwords masked by default, and export the results as a proxy list file in host:port, URL, or CSV format.

Instructions

List the static IPs of an ISP subscription. Passwords are masked unless reveal_passwords is true. Set export_format to save a proxy list file (owner-only permissions) instead.

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>"
    },
    "name": "isp_proxies"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No
`export_format`	No
`subscription_id`	Yes
`reveal_passwords`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.6/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 safety profile is covered. The description adds genuinely new behavior: passwords are masked by default and only revealed via reveal_passwords, and exported files carry owner-only permissions — both non-obvious side effects an agent should know before calling.

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?

Three short sentences, each carrying distinct information, with the core action front-loaded. The trailing 'instead' is slightly ambiguous about what exactly is being replaced, but no sentence is wasted.

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?

With no output schema, the description should ideally hint at the returned shape, and the undocumented 'path' parameter leaves a gap for a tool that can either return IPs or write a file. The masking and file-permission notes cover the most important behavioral risk, so it is adequate but incomplete.

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?

Schema description coverage is 0%, so the description must carry the load. It meaningfully explains reveal_passwords (default masking behavior) and export_format (writes a file instead of returning data), but says nothing about the 'path' parameter or what subscription_id must reference, leaving half the parameters undefined.

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: 'List the static IPs of an ISP subscription.' That is enough to distinguish it from credential, invoice, or order siblings, though it never names the closely related export_proxy_list tool.

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?

Gives one concrete routing cue — use export_format when you want a saved proxy list file instead — but frames it as a parameter switch rather than naming the dedicated export sibling. No guidance on when the masking default should be overridden or on subscription selection.

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