Skip to main content
Glama

proxy_network

Check whether Browsa's built-in proxy network is enabled and list available tiers, exit countries, and credit price per GB before starting a browser with a proxy.

Instructions

Say whether Browsa's built-in proxy network is enabled on this server and, when it is, list its tiers (datacenter, residential) with the exit countries of each and the price per GB in credits. Call this before passing proxy {"network": ...} to start_browser. When enabled is false, only your own proxy can be used.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and clearly establishes that this is an informational read operation. It discloses the key behavioral implication of the result, including that a disabled network limits proxy use to the caller's own proxy, though it does not discuss permissions, errors, or rate limits.

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?

The description is three tight sentences. It front-loads what the tool reports, then the usage instruction, then the disabled-network consequence, with no redundant wording.

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?

For a zero-parameter, annotation-free informational tool without an output schema, the description covers what will be reported, when to call it, and the important disabled-state implication. It gives an agent enough context to use the tool correctly without needing more structured metadata.

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?

The tool takes zero parameters, so there are no parameter semantics to explain beyond the schema. The description appropriately focuses on the returned information and the downstream start_browser usage.

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?

The description states a specific informational action: report whether Browsa's built-in proxy network is enabled and, if so, list tiers, exit countries, and price per GB. It clearly distinguishes this capability from start_browser by framing it as a prerequisite check before passing proxy configuration.

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?

It explicitly says to call this before passing proxy {"network": ...} to start_browser. It also states the consequence when enabled is false: only the caller's own proxy can be used, which gives clear decision guidance.

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