Skip to main content
Glama

US Company Intelligence for AI Agents (SEC EDGAR, x402)

by online.x-402
OverviewDiscussionsAdmin

proxy_1gb

Get a working HTTP/HTTPS proxy on a real French home line (Caribbean, Outremer Telecom) with 1 GB of traffic, as a key you use in curl -x, valid 30 days. Buy 1 GB of French West Indies residential proxy bandwidth for scraping and agent traffic, delivered as a ready-to-use key in the form http://buyer:KEY@host, valid 30 days and metered per gigabyte at 3.50 USD. The exit is a real FTTH home line in the French West Indies on Outremer Telecom / SFR Caraibe (AS20776), reverse DNS ftthcc.*.sfrcaraibe.fr. Geolocation is split across databases and we say so rather than pick the flattering one: ipinfo and ipwho.is place it in Martinique (MQ), ip-api and db-ip place it in mainland France (FR). Reachability, carrier and proxy-blacklist status are probed from the public internet before every sale: the address currently comes back clean, not flagged as a proxy or VPN. If no exit is verified live you are not charged. A Caribbean residential exit is rare, so a site fingerprinting by region sees an address no datacenter range can imitate. — $3.500000/call, paid per request via x402 (USDC). Use when asked: "residential proxy, pay per gb", "get a residential ip for my agent", "http proxy with a french home ip".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / exit
      Removed value: -{
-  "type": "string"
-}
  2. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
-  "exit"
-]
  3. Changed2 schema fields changed
    • addedInput schema / properties / exit
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "exit"
+]
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations to help, the description carries the full burden and does so thoroughly: it discloses delivery key format, 30-day validity, metering, pricing, the real FTTH exit, geolocation database disagreement, pre-sale probing, and the no-charge guarantee if no live exit is verified.

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?

Information-dense and front-loaded, but the first two sentences repeat the 1 GB/30-day facts, and the final marketing sentence is slightly expendable. Overall, the length is justified by the detail.

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?

Even without an output schema, the description explains the returned artifact's format, payment method, validity, usage, and geographic properties. An agent has enough context to know when to call and what to expect.

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 input schema has zero parameters, so the baseline is 4. No parameter explanation is needed; the description appropriately focuses on what the user receives rather than inputs.

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?

Opens with a specific verb and resource: 'Get a working HTTP/HTTPS proxy... with 1 GB of traffic, valid 30 days.' It clearly defines what is being sold and implicitly distinguishes from proxy_5gb/proxy_20gb by specifying the 1 GB tier and Caribbean residential exit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Ends with explicit trigger phrases: 'Use when asked: "residential proxy, pay per gb", "get a residential ip for my agent", "http proxy with a french home ip"'. This is strong, but it does not explicitly rule out or route to sibling proxy sizes.

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

All US Company Intelligence for AI Agents (SEC EDGAR, x402) toolsInspect
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.

Resources