Skip to main content
Glama
fouradata

@fouradata/mcp

Official

FourA - HTTP request via rotating proxies

foura_proxy
Read-only

Route HTTP requests through rotating proxies with automatic retry. Bypass IP blocks and enforce exit-country rules, with per-attempt validation to get reliable responses.

Instructions

Route an HTTP request through rotating proxies with automatic retry. Use it when foura_single is blocked or the target requires a specific exit country. The response includes the proxy ID that succeeded; reuse it with foura_single or foura_browser, or exclude it with ignoreProxies. Use foura_browser when the page needs JavaScript. Set exitCountries for a strict country allowlist, and request.browser, request.os, or request.version to present a different browser.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesThe inner HTTP request to send through each proxy attempt. Validation rules here determine when a proxy is treated as failed and retried.
maxTriesNoMaximum rotation attempts before giving up (default 5, max 90). Difficult protected targets may need 25-30. Use exitCountries for country scope.
timeout_msNoOverall timeout across all rotation attempts in ms (default 45000, max 120000). Must be positive.
exitCountriesNoOptional target-visible proxy countries as two-letter provider codes, for example ["CZ", "GB"]. Use codes supplied by the user or target requirements. When geography matters, do not guess codes or substitute unscoped rotation. Values are trimmed, uppercased, and deduplicated. Unknown exits are excluded and the request never falls back to another country.
ignoreProxiesNoEncoded proxy IDs (base36 strings like "4DZ3VE") or proxy URLs to exclude from rotation.
offload_largeNoIf true, response bodies of 50 KB or more are returned as a resource_link instead of inlined. Default false. Read the returned offloaded_resource_uri with resources/read.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoStable error code for retry classification. auth_failed means the FourA API key was rejected; verify that key, not target-site credentials. no_eligible_proxy means the strict exitCountries scope had no match. Keep that scope and retry later; do not propose or perform an unscoped fallback.
dataNoDecoded response body. Omitted when offloaded.
errorNoHuman-readable error message
proxyNoBase36 ID of the exit that succeeded (e.g. `4DZ3VE`). Pass it to foura_single.proxy or foura_browser.proxy to reuse that exit, or to foura_proxy.ignoreProxies to skip it on future rotations.
totalNoOuter total time in seconds (proxy selection + retries + the successful inner attempt). Float.
limitsNo
statusNoHTTP status code from the target (from the succeeding proxy attempt). `0` indicates every attempt failed before any HTTP response (DNS / connection refused / timeout) - check the `error` field for the underlying reason.
currentNo
defenseNoPresent when the target ran a bot check. When solved is false the body may be a challenge page: retry with a different browser, os, or version, or move to foura_browser.
detailsNoStructured no_eligible_proxy context containing the normalized requested country scope. Preserve this scope and retry later. Do not propose or perform an unscoped fallback; change it only after the user explicitly changes the requirement.
headersNoResponse headers per redirect hop, as an array of objects. Each entry has `result.{version, code, reason}` plus arbitrary header-name keys whose values are strings (or arrays of strings for multi-value headers like Set-Cookie / Link).
requestNoEchoed PrRequest from upstream PrResponseError
serviceNo
retryAfterNo
size_bytesNoTotal offloaded body size in bytes
total_timeNoPer-attempt wall-clock duration of the succeeding inner request
exitCountryNoLatest available two-letter target-visible exit-country code used for selection. Present on successful requests that use exitCountries.
offloaded_resource_uriNofoura-mcp://payload/<uuid>. Pass this URI to resources/read to retrieve the offloaded body.
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context beyond that: automatic retry, the response including the proxy ID, and its reuse/exclusion with ignoreProxies. No contradictions.

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?

Three sentences, front-loaded with purpose, no fluff. Each sentence contributes: what it does, when to use it, and how to work with the response.

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?

The description covers the essential decision points (when to use, exit countries, JavaScript handling, proxy reuse) and is supported by a rich schema and output schema. It does not detail parameters like maxTries or offload_large, but those are well-documented in the schema.

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 description coverage is 100%, so the schema already documents all parameters. The description mentions exitCountries and request.browser/os/version, but these are already in the schema; it adds no new per-parameter meaning beyond connecting proxy ID reuse to ignoreProxies.

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 verb and resource: 'Route an HTTP request through rotating proxies with automatic retry.' It explicitly distinguishes this tool from siblings by naming foura_single and foura_browser, making its role clear.

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?

Provides explicit when-to-use guidance: 'Use it when foura_single is blocked or the target requires a specific exit country' and 'Use foura_browser when the page needs JavaScript.' This gives clear context and names alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fouradata/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server