SoftGlaze Browser MCP

Overview Schema Source Related Servers Discussions Admin

Check a proxy

check_proxy

Idempotent

Tests a saved proxy connection and reports its exit IP, country, city, ISP, timezone, and speed, saving results to the proxy without changing any profile.

Instructions

Connects through a saved proxy now and reports whether it works, its exit IP, country, city, ISP, timezone and speed. The result is saved on the proxy. Does not change any profile.

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": {
      "id": "<id>"
    },
    "name": "check_proxy"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Proxy id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description usefully explains the write side effect ('The result is saved on the proxy'), which justifies readOnlyHint=false and adds context annotations cannot convey. It also mentions scope ('Does not change any profile'). Missing are auth requirements, latency/timeout expectations for a live connection test, or whether a failed check is still persisted — notable gaps given openWorldHint=true means it hits an external endpoint.

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?

Two sentences, front-loaded with the action and result fields, then the side effect and scope limit. The field enumeration is slightly list-heavy but each item tells the agent what comes back, so little is wasted.

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 one-parameter, no-output-schema tool, the description covers what it does, what it returns, where the result goes, and confirmed non-targets. The main omission is failure behavior — what the agent sees when the proxy does not work and whether that result persists.

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 coverage is 100% and the single parameter is fully documented as 'Proxy id', so the schema does the work. The description only implies via 'saved proxy' that the id must reference a stored proxy; it adds no format or lookup detail beyond that.

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 ('Connects through a saved proxy now and reports whether it works') and enumerates the returned facts (exit IP, country, city, ISP, timezone, speed). It is clearly distinguishable from assign_proxy or rotate_proxy_ip, though it never names get_proxy_health to clarify how a live check differs from stored health.

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?

'now' implies an immediate live test rather than reading stored data, and 'Does not change any profile' sets a negative boundary. However there is no explicit when-to-use/when-not-to-use guidance and no routing to a sibling such as get_proxy_health for historical results, so the agent must infer the choice.

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