ProxyRange

Compare residential proxy providers

compare_providers

Read-onlyIdempotent

Two to four residential proxy providers side by side: checkout prices for 1, 10 and 100 GB with which one is cheaper at each (regular prices only), smallest first purchase, traffic expiry, ID check, trial, refunds, protocols, targeting, sticky sessions, payments, testing terms, sourcing checks, our best-for lines, and whether any of them share infrastructure.

Input Schema

Name	Required	Description	Default
`providers`	Yes	Two to four provider ids, names or websites

Output Schema

Name	Required	Description
`licence`	Yes
`updated`	Yes	The newest date any fact in the data was checked (YYYY-MM-DD)
`cheaperAt`	Yes
`notStated`	Yes
`providers`	Yes
`sharedNote`	Yes
`attribution`	Yes	How to credit the data when you show it
`sharedInfrastructure`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

addedOutput schema / properties / sharedInfrastructure / items / properties / evidence
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

addedOutput schema / properties / sharedInfrastructure / items / properties / firstSeen

Added value: +{
+  "anyOf": [
+    {
+      "description": "YYYY-MM-DD",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / sharedInfrastructure / items / properties / lastSeen

Added value: +{
+  "anyOf": [
+    {
+      "description": "YYYY-MM-DD",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / sharedInfrastructure / items / required

Previous value: -[
-  "between",
-  "how"
-]New value: +[
+  "between",
+  "how",
+  "evidence",
+  "firstSeen",
+  "lastSeen"
+]

addedOutput schema / properties / sharedNote
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "providers",
-  "cheaperAt",
-  "sharedInfrastructure",
-  "notStated",
-  "updated",
-  "attribution",
-  "licence"
-]New value: +[
+  "providers",
+  "cheaperAt",
+  "sharedInfrastructure",
+  "sharedNote",
+  "notStated",
+  "updated",
+  "attribution",
+  "licence"
+]

First observedOct 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description still adds real behavioral context beyond that: the comparison is limited to regular prices (excluding promo pricing), which materially affects what the agent can claim the output means, plus the scope of checked attributes including sourcing checks and shared infrastructure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, which is good. But the remainder is a single run-on sentence stringing together roughly fifteen comma-separated attributes with no grouping or priority, making it harder to scan than a shorter summary plus a shortlist would be.

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?

An output schema exists, so return values need no explanation, and read-only annotations cover side effects. What remains unstated is edge-case behavior — an unknown/ambiguous provider name, or whether one of the listed comparison dimensions can be missing for some providers — which matters for a 2-4 element input.

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 property description already explains that ids, names, websites, and former names (e.g. 'Smartproxy') are accepted. The description's only parameter-adjacent fact, 'two to four providers', is already encoded as minItems=2/maxItems=4, so it adds nothing beyond the schema.

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?

Names a specific operation (side-by-side comparison) on a specific resource (2-4 residential proxy providers) and enumerates the dimensions compared, so an agent knows this is the multi-provider comparison tool rather than the single-provider get_provider or the narrower cheapest/shared_infrastructure lookups. It never names those siblings explicitly, so the boundary with 'cheapest' and 'shared_infrastructure' — both of which are partially subsumed here — is left for the agent to infer.

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: the 'two to four providers side by side' phrasing signals the multi-provider comparison case, and the schema's minItems/maxItems reinforce it. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives for a single provider or a cheapest-only question.

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

All ProxyRange tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.