Skip to main content
Glama

Lilambd Data for Agents

world-outages

Which cloud and SaaS providers have an outage open right now, and what did they publish?. Incidents that 39 providers (AWS, Azure, Microsoft 365, Google Cloud, GitHub, Cloudflare, Slack, Zoom, OpenAI, Anthropic, Shopify, Twilio and more) published on their own official status pages, collected every 2 minutes from official public feeds. Every row links to the provider's own incident page. Nothing is estimated or rated. Routes: /open (provider, limit); /same-day (date, limit); /incidents (provider, since, until, impact, limit, offset); /providers (limit). Paid $0.01 USDC per call via x402 (_meta["x402/payment"]); set sample=true for a free 3-row preview.

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": {
      "route": "<route>"
    },
    "name": "world-outages"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /open, /same-day, /incidents, /providers. Replace {placeholders} with a value, e.g. /search or /HND.
paramsNoQuery parameters, e.g. {"q":"tokyo","limit":"50"}
sampleNoFree preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses provenance (official public status pages, collected every 2 minutes), a no-estimation/no-rating policy, per-row links to the source incident page, and the payment model ($0.01 USDC per call via x402, with a free 3-row sample). These are exactly the behavioral facts an agent needs before spending money on a call.

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 the core question, then provenance, routes, and pricing in a logical order. Dense but nearly every clause earns its place; the long parenthetical provider roster is the only mildly expendable element.

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?

No output schema exists, and the description covers the essentials: rows link to the provider's own incident page and nothing is estimated or rated. It does not describe the returned field set or pagination semantics for offset/limit, which leaves a small gap for a multi-route data tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the schema's route description is generic boilerplate referencing nonexistent routes (/search, /HND). The description compensates by mapping each real route to its accepted parameters (/open: provider, limit; /incidents: provider, since, until, impact, limit, offset), which is meaning the schema does not supply.

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 question naming the exact resource (cloud/SaaS provider outages open right now) and the payload (what they published), then enumerates the four routes. An agent knows precisely what this returns 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?

The route list effectively tells the agent which route serves which need (/open for current, /same-day for a date, /incidents for historical filtering, /providers for the roster), and the sample=true free preview is called out. It stops short of explicit when-not-to-use guidance, but the sibling tools are unrelated domains so no alternative routing is needed.

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