Lilambd Data for Agents

signals

Lilambd World Signals Daily Change by Country. What changed today in the world's news events, per country. Daily GDELT 2.0 event counts by country and CAMEO root code (20 event types from public statement to mass violence) with mean Goldstein score, collected every morning since 2026-09-22: 19,185 country x event-type rows covering 126,256 events in 228 GDELT country codes over 31 collected days (2026-09-22 to 2026-11-03; 12 days not collected). One call to /today/{iso2} returns today's totals for a country against the previous collected day and the 7-day baseline, its rank, conflict share and the biggest changes by event type. Also: rankings, rising country x event pairs, time series per country. Source: Lilambd/world-signals (CC BY 4.0), GDELT Project (free with attribution). Routes: /days; /gaps; /rank (by, min_events, date, limit, offset); /cameo; /events (country, cameo, date, limit, offset); /rising (min_events, date, limit, offset); /countries; /cameo/{root} (date, limit, offset); /today/{iso2} (date); /country/{iso2} (days, date, 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": "signals"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /days, /gaps, /rank, /cameo, /events, /rising, /countries, /cameo/{root}, /today/{iso2}, /country/{iso2}. 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.7/5.0

Behavior4/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 well: it discloses the paid x402 model ($0.005 USDC per call), the free 'sample=true' 3-row preview escape hatch, the data collection gaps (12 days not collected), and licensing/attribution requirements. It falls short of full marks because it says nothing about rate limits, failure modes, or what the non-/today routes actually return.

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 opening clauses front-load the core purpose before the dense route inventory, and no sentence is pure boilerplate. The row/event/day count statistics (19,185 rows, 126,256 events, 228 codes) are somewhat decorative and could be trimmed, but the overall structure is functional and scannable.

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 multi-route, nested-parameter tool with no output schema and no annotations, the description covers cost, coverage window, and route names, which is a solid base. It is still incomplete: return shapes for nine of ten routes are undescribed, per-parameter meaning is absent, and error/pagination behavior is unaddressed.

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%, so 3 would be the baseline, but the description goes beyond it by mapping each route to its accepted query parameters (e.g. '/rank (by, min_events, date, limit, offset)') — information the generic 'params' additionalProperties object cannot convey. It loses a point because the semantics of individual parameters such as 'by' or 'min_events' are never explained, only listed.

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 resource concretely (daily GDELT 2.0 event counts by country and CAMEO root code, with mean Goldstein score) and states what changes it captures. It is clearly distinguishable from generic data APIs, but it never differentiates itself from siblings like 'rising', 'conflict', or 'pulse', which appear to cover overlapping territory.

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?

Usage is implied through the route inventory (e.g. '/today/{iso2}' for today vs previous collected day, '/rising' for rising country x event pairs), so an agent can infer which route fits which question. However, there is no explicit when-to-use/when-not guidance and no statement about when to call this instead of the sibling 'rising' or 'conflict' 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?