Skip to main content
Glama
fusionproxy-mcp

fusionproxy-mcp

Official

check_exit_ip

Verify the public IP address, location, and network that websites see through the proxy, optionally for a chosen country or sticky session.

Instructions

Show the IP address, location and network that websites see through the proxy.

Args: country: two-letter country code of the exit IP. Optional. session: session name to check a sticky IP. Optional.

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

Input Schema

NameRequiredDescriptionDefault
countryNo
sessionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it leaves key traits undisclosed: whether the call consumes quota/bandwidth, whether naming a new session creates one or fails, and whether the probe has any side effect on the sticky session it inspects. The single strength is that it names the observation point (what websites see), which clarifies the network path being measured.

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?

The operative sentence is front-loaded and complete, and the parameter notes are compact and grouped. Slight redundancy in the "Optional" notes, which restate the schema defaults, but overall there is no wasted text.

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?

This is a simple two-optional-parameter read tool, and the presence of an output schema means return values need not be described. Still, for a tool with zero annotation coverage the definition should say what the default invocation does and whether checking a session has side effects or costs, which it omits.

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 schema contributes only bare titles ("Country", "Session"), and the Args block genuinely compensates: it specifies the two-letter format for country and that session targets a sticky IP, plus marks both optional. It stops short of stating the behavior when both are omitted or how country interacts with session.

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?

"Show the IP address, location and network that websites see through the proxy" states a specific verb and a precisely scoped resource (the externally visible exit IP). An agent immediately knows the diagnostic function; the only thing missing is any explicit contrast with sibling tools, which is a minor gap given fetch_page is clearly unrelated.

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: an agent infers it should call this to verify the proxy route it is actually exiting from. The Args block hints that passing a session checks a specific sticky IP, but there is no explicit statement of when to omit both args (e.g. checking the default/rotating route) and no exclusions or prerequisites.

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