Lilambd Data for Agents

disaster-exposure

How many deadly earthquakes, tsunamis and eruptions has this place seen since 1900?. Give a point (lat, lon) and a radius. Returns NOAA NCEI significant earthquake, tsunami and volcanic eruption records within that radius since a chosen year: counts by kind, published deaths on the records, strongest quake magnitude and the five deadliest records with distance. Plus a per-decade table. Counts and distances computed by Lilambd from NOAA records; no personal data. Routes: /; /answer (lat*, lon*, radius_km, since); /decades (kind, limit, offset). Paid $0.5 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": "disaster-exposure"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /, /answer, /decades. Replace {placeholders} with a value, e.g. /search or /HND.
`params`	No	Query parameters, e.g. {"q":"tokyo","limit":"50"}
`sample`	No	Free preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description does a good job of disclosing cost ($0.5 USDC per call via x402), the sample preview behavior, and data provenance (computed by Lilambd from NOAA records, no personal data). However, it says nothing about rate limits, failure behavior when a point has zero records, or what the response envelope looks like beyond the enumerated content.

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 purpose and the returned content, then routes, then payment, which is the right order for a caller. The density is high and a few clauses (e.g. the producer attribution sentence) could be tightened, but nothing is redundant.

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?

For a three-field, nested-params tool with no annotations and no output schema, the description covers purpose, routes, parameters, response contents, pricing, and preview mode, which is enough to invoke it correctly. Minor omissions are the default since-year and how errors or empty results are reported.

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 100%, but the schema only exposes a generic route/params object, so the description is what actually names the real parameters: lat, lon, radius_km, since for /answer and kind, limit, offset for /decades. That is genuine value beyond the schema, though it stops short of stating formats, units, or defaults for since.

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 concrete question-shaped framing (deadly earthquakes, tsunamis, eruptions at a place since 1900) and states the verb+resource precisely: returns NOAA NCEI significant-event records within a radius with counts, deaths, magnitude, and top-five deadliest. It is unambiguous what the tool produces, though it never names how it differs from nearby siblings such as hazard or exposure.

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 gives clear input requirements (a point plus radius, optional since-year) and enumerates the three routes with their parameters so the caller knows which route to pick. It also explains the free-preview escape hatch via sample=true. The gap is that it gives no guidance on choosing this tool over sibling hazard/exposure tools.

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

All Lilambd Data for Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?