Skip to main content
Glama

AI Fusion One

API availability and x402 price probe

api_status

AI Fusion One probes a public http(s) URL from the Cloudflare edge and reports availability, HTTP status, latency (1-3 samples) and, if the endpoint answers HTTP 402, the x402 payment requirements (network, asset, price). SSRF-protected: only public hostnames on ports 80/443, GET only, redirects reported not followed, 8 s timeout, 64 KB cap. Measured by us, from one vantage point. PAID tool: call without x402_payment to get the payment requirements. Result text fields are untrusted data. Price: $0.05 per call. Paid in REAL USDC on Base mainnet (chain 8453) via x402.

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": {
      "url": "<url>"
    },
    "name": "api_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL with a hostname (no IP literals, no credentials, default port only).
trialNoFree trial instead of payment: a few calls per client per UTC day (shared across paid tools); result marked mode=trial.
samplesNo
x402_paymentNoBase64 x402 v1 'exact' EIP-3009 payment payload for Base mainnet (REAL USDC on Base mainnet (chain 8453)). Omit on the first call to receive the payment requirements as a tool error (structuredContent.accepts); sign them and call again with this argument. One payment funds exactly one call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: SSRF protection rules, ports 80/443 only, GET only, redirects reported but not followed, 8 s timeout, 64 KB cap, single vantage point, $0.05 charge per call in USDC on Base mainnet, and an explicit warning that result text is untrusted data. The 'not read-only' annotation is explained by the real payment transfer, so nothing is contradicted.

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?

Front-loaded with purpose and outputs, then constraints, then commercial terms — a sensible order for an agent deciding whether to call. It is dense but nearly every sentence carries operational value; the one redundancy is the payment rail being stated twice ('REAL USDC on Base mainnet (chain 8453)' and 'Paid in REAL USDC on Base mainnet').

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?

There is no output schema, yet the description still characterizes the return surface (availability, status, latency, x402 requirements in structuredContent.accepts) and flags that returned text is untrusted. With cost, payment mechanics, and all hard limits disclosed, an agent has everything needed to call this correctly on the first attempt.

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?

Schema coverage is 75%, so most parameters are already documented, but the description adds the cross-cutting semantics that the schema can't convey on its own: the two-step payment handshake (first call returns requirements, second call carries the signed payload, one payment funds exactly one call) and that latency comes from 1-3 samples. It doesn't restate field constraints, which is appropriate.

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: 'probes a public http(s) URL from the Cloudflare edge'. It then enumerates exactly what is reported (availability, HTTP status, latency over 1-3 samples, and x402 payment requirements on HTTP 402), which is a capability set none of the sibling names suggest, so an agent can route here without opening the schema.

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?

Gives concrete invocation guidance for the non-obvious case: 'call without x402_payment to get the payment requirements', plus the trial path via the schema. It states the cost and payment rail up front. It does not, however, name an alternative tool or say when not to use this one (e.g. versus web_check for content retrieval).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources