Skip to main content
Glama
Sign In
DoubleData MCP

DoubleData MCP

by doubledata-proxy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ISP proxy catalog

isp_catalog
Read-only

View ISP static residential proxy tiers, in-stock countries, add-on features, and pricing to compare proxy options before purchasing.

Instructions

Show ISP (static residential) proxy tiers, available countries with stock, add-on features and prices.

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_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 supplied. The description adds the payload content (tiers, country stock, add-ons, prices), which is valuable with no output schema, but it says nothing about auth requirements, price currency/units, or whether stock is live.

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?

One dense sentence that front-loads the resource and enumerates the returned data. Nothing is wasted or buried.

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 parameterless read tool with no output schema, the description covers the essentials of what comes back (tiers, country stock, add-ons, prices). Minor gaps remain on currency/unit semantics and whether prices are quoted before ordering, but nothing critical is missing.

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?

Zero parameters, so the baseline of 4 applies; the schema is empty and the description correctly does not invent parameter behavior.

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 ('Show') and resource ('ISP (static residential) proxy tiers'), and enumerates the contents: countries with stock, add-on features, and prices. That lets an agent distinguish it from order/quote siblings, 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 only implied: it reads as a pre-purchase browse step before isp_quote or isp_order. There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named.

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

Deploy Server

Other Tools