proxy-finder-mcp

List available countries

list_countries

Lists countries covered by the merged proxy pool with proxy counts per country. Use it to discover valid country codes before requesting a proxy via find_proxy.

Instructions

Lists the countries currently covered by the merged proxy pool, with a proxy count per country. Use this to discover what country codes are worth passing to find_proxy before asking for one.

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

Input Schema

Name	Required	Description	Default
`forceRefresh`	No	Bypass the cached proxy list and re-fetch all sources.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the data source (merged proxy pool) and that results reflect currently covered countries, but says nothing about caching or freshness — the cache/refresh behavior is only visible in the forceRefresh parameter schema, not the description.

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?

Two tight sentences, zero waste, with the core behavior front-loaded before the usage routing. Nothing is padded.

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?

Though there is no output schema, the description explains the return shape (countries with per-country proxy counts), which is what an agent needs. The only omission is the freshness/caching dimension that forceRefresh hints at.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents forceRefresh fully. The description adds no information about the parameter, which is acceptable given the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists the countries') plus the scope ('currently covered by the merged proxy pool') and the return shape (a proxy count per country). This clearly distinguishes it from find_proxy, check_proxy, and list_proxies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this to discover country codes worth passing to find_proxy 'before asking for one.' Names the alternative sibling and the ordering condition that selects it.

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

Deploy Server