Skip to main content
Glama

Lilambd Data for Agents

hazard

World Natural Hazards and Warming. How much each place shakes and how much it has warmed, in one API. Every number is counted or averaged from public measurement records; nothing is modelled. Routes: /gaps (level, country, min_population, limit, offset); /events (kind, country, region, from, to, min_deaths, min_magnitude, lat, lon, radius_km, sort, limit, offset); /trends (band); /regions (q, country, sort, joint_exposure, lat, lon, limit, offset); /summary; /stations (country, q, sort, lat, lon, radius_km, limit, offset); /countries (sort, limit, offset); /place-risk (lat*, lon*, radius_km); /events/{id} (kind); /regions/{id} (events); /features/{id}; /stations/{id}; /joint-exposure (limit, offset); /countries/{iso2}; /regions/{id}/events (kind, sort, limit, offset); /regions/{id}/stations (limit, offset). Paid $0.005 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": "hazard"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /gaps, /events, /trends, /regions, /summary, /stations, /countries, /place-risk, /events/{id}, /regions/{id}, /features/{id}, /stations/{id}, /joint-exposure, /countries/{iso2}, /regions/{id}/events, /regions/{id}/stations. 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

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden. It discloses pricing ($0.005 USDC via x402), a free sample limit, and provenance (counted/averaged public measurements, nothing modelled). It omits payment flow details, rate limits, and error behavior.

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?

The one-line purpose is front-loaded, then the route list; every route entry conveys invocation information. The parenthetical parameter lists are dense but appropriate for a 17-route router tool.

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?

For a complex multi-route tool with no output schema, the description gives enough to select a route and supply basic params, plus cost/sample behavior. It leaves out return-value expectations and parameter value semantics, which leaves gaps for correct invocation.

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 schema covers route/params/sample generically, but the description adds route-specific parameter lists (e.g., /events supports kind, country, from/to, min_deaths, etc.) and required placeholders. It still does not define accepted values for kind, sort, band, or country formats.

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 names the domain (natural hazards and warming), states the data are measured, and enumerates 17 routes, so an agent can tell it is a multi-endpoint hazards/warming API rather than one of the sibling tools. It does not explain what the individual routes return, so purpose is clear at the API level but not route level.

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

Usage Guidelines3/5

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

It gives route-specific query parameters and notes paid per-call and free sample preview, implying how to use the tool. It does not say when to choose one route over another, nor any alternative tool or prerequisite beyond payment.

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