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. TESTNET ONLY: priced in Base Sepolia test USDC (no real value).

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 Sepolia (TESTNET test USDC, no real value). 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.3/5.0
Behavior5/5

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

The annotations (readOnlyHint false, openWorldHint true, idempotentHint false) say little about what actually happens, so the description carries real weight here. It discloses the SSRF constraints (public hostnames, ports 80/443, no IP literals, GET only), the 8 s timeout, the 64 KB cap, that redirects are reported not followed, that results are measured from one vantage point, that result text is untrusted data, and that the tool is paid at $0.05/call in testnet USDC. That is exactly the behavioral context an agent needs before invoking a paid, open-world probe.

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?

It is front-loaded with the core action, then follows with guards, payment protocol, provenance caveat, price and testnet disclaimer in a sensible order. Every sentence is informative, though a few constraints (URL restrictions) duplicate what the input schema already states.

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, and the description compensates by enumerating the returned fields (availability, HTTP status, latency, x402 requirements with network/asset/price). For a paid, open-world probe with a non-trivial two-call payment handshake, the definition leaves nothing material unexplained.

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 url and x402_payment are already documented. The description still adds value by explaining the two-step payment protocol ('Omit on the first call to receive the payment requirements... sign them and call again') and by stating that one payment funds exactly one call. It mentions 1-3 samples but does not say what the samples parameter changes in behavior, leaving that to 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?

The description opens with a specific verb and resource: 'probes a public http(s) URL from the Cloudflare edge and reports availability, HTTP status, latency... and x402 payment requirements.' That is far more precise than the bare name api_status. It does not, however, distinguish itself from the sibling web_check, so an agent cannot rule out overlap from this text alone.

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?

It clearly explains the call sequence: call without x402_payment first to receive the payment requirements, then sign and call again. It also names the trial alternative ('Free trial instead of payment') and scopes it with quota details. The gap is that it never names a sibling or states when a different URL-checking tool would be the better choice.

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