Skip to main content
Glama

Ai infra status

ai_infra_status
Read-onlyIdempotent

Live outage & latency status radar across 9 AI + crypto backbone providers (OpenAI, Anthropic, Cloudflare, GitHub, Stripe, Coinbase, Base, Solana, Hyperliquid). 60s cached (<5ms) for high-frequency agent pre-flight checks. Free live board: https://apexfaucet.xyz/pulse/ . $0.001 per call over x402 or X-API-Key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ai_infra_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
categoryNoOptional provider category filter (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the description's job is to add context — and it does: 60s cache TTL with <5ms served latency (implying data can be up to a minute stale) and a per-call price via x402 or X-API-Key. It does not describe response shape or failure behavior, but the auth/cost/staleness disclosures are the high-value ones for this tool.

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?

Three dense sentences, front-loaded with what the tool returns and how fresh it is, followed by pricing. The 'Free live board' URL is partly promotional, but it is a legitimate escape hatch for a human checking the same data and costs little space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 never indicates what a result entry contains (status enum, latency numbers, per-provider granularity) — an agent must call blind to learn the shape. Coverage of cost, caching and provider list is solid, but the return-value gap is notable for a tool with no output 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 coverage is 100%, so both the payment payload and the category enum are already documented in structured form; the baseline of 3 applies. The description adds only that payment is billed at $0.001 per call over x402 or X-API-Key, which clarifies the payment param's model but not its format.

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?

States a specific verb and resource — 'Live outage & latency status radar' — and enumerates the exact 9 providers covered, so an agent knows precisely what data comes back. It is clearly distinct from siblings like cve_lookup or url_threat_check, which target single-item security lookups rather than provider-wide health.

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?

Explicitly frames the intended use case: 'high-frequency agent pre-flight checks,' which tells an agent when to reach for it. It does not name a when-not condition or an alternative sibling for related questions (e.g., package_audit for dependency risk), so it stops short of full routing guidance.

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