Skip to main content
Glama

proxy_check

Test a proxy URL before binding it to an identity, returning exit IP, country, and latency or a clear error so dead or slow exits are caught early.

Instructions

Test a proxy URL and report where it actually comes out. No identity needed.

Use it before binding a proxy to an identity with profile_create: a dead or slow exit found here costs nothing, the same exit found halfway through a signup costs the account.

Args: url: the proxy URL to test, e.g. "http://user:pass@host:port" or "socks5://host:port".

Returns {ok: true, exit_ip, country, latency_ms} when the proxy works, or {ok: false, error} when it does not. A dead proxy is an ANSWER, not a failure — check the ok field rather than assuming success. Note that country can be null even on a working proxy if the exit IP cannot be geolocated.

This tests a bare URL. To test the proxy an identity is already bound to, the daemon's per-identity check is a separate endpoint not yet exposed here.

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the return shape for both success and failure, warns that a dead proxy returns ok:false rather than erroring ('an ANSWER, not a failure'), and notes country may be null on a working proxy. It also notes no identity/auth is needed.

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?

Front-loaded with the purpose and the key warning, then structured Args/Returns. Slightly long and the Args block partially duplicates the schema, but every line adds usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description documents the return fields (ok, exit_ip, country, latency_ms, error) and their edge cases. Nothing an agent needs to call and interpret this tool 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?

Schema coverage is 0% for the single required url parameter, but the description compensates with concrete format examples (http with embedded credentials, socks5). A 4 rather than 5 because port/credential edge cases and validation rules are not described.

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: 'Test a proxy URL and report where it actually comes out.' No sibling tool does proxy testing, so this is unambiguous and immediately distinguishable from profile_* and session_* tools.

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 says to use it before binding a proxy with profile_create, gives the rationale (failure here is free, failure mid-signup costs the account), and explicitly states what it does NOT cover (per-identity check not exposed). This is textbook when/when-not guidance.

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