Lilambd Data for Agents

pulse

World Pulse Daily Tech and Money Briefing. What moved in tech and money today, from public catalogues that only ever show today. Lilambd writes them down every day, so they become a history. Routes: /fx (base, to, amount, date); /days (limit); /feeds; /today (date); /search (q*, feed, from, to, history, limit, offset); /changes (since, date, feed, kind, type, min_change_pct, limit, offset); /briefing (date); /feeds/{feed} (date, kind, q, sort, limit, offset); /feeds/{feed}/history (key, q, kind, from, to, 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": "pulse"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /fx, /days, /feeds, /today, /search, /changes, /briefing, /feeds/{feed}, /feeds/{feed}/history. 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 behavioral burden. It discloses important non-obvious traits: paid $0.005 USDC per call via x402 (_meta["x402/payment"]), sample=true gives a free 3-row preview, and the data becomes historical because the underlying catalogues only show today. It does not cover rate limits, error behavior, or response format, but the cost and access model are clearly surfaced.

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 description is dense but well structured: purpose first, then a compact route/parameter listing, then pricing and free-preview behavior. The route list is long, but for a multi-route router tool that information is necessary. There is little wasted wording, though the route block is hard to scan as plain prose.

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 tool with no output schema and no annotations, the description covers the available routes, their parameter names, payment requirements, and the sample preview. However, it does not explain return values or response shape for each route, and parameter formats such as dates and amounts are unspecified. That leaves meaningful gaps for correct invocation, especially across nine routes.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful per-route parameter semantics that the generic 'params' object cannot convey. It maps route-specific fields such as /fx (base, to, amount, date), /changes (since, date, feed, kind, type, min_change_pct, limit, offset), and /search (q*, feed, from, to, history, limit, offset). It still does not specify types or formats for those fields.

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 states a specific resource and scope: a 'World Pulse Daily Tech and Money Briefing' covering what moved in tech and money today. It also names concrete routes (/fx, /days, /feeds, /search, etc.), which makes the tool's multi-route briefing purpose clear. Sibling tools are mostly unrelated, so no further differentiation is needed.

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?

The route list implies usage, e.g. /fx for FX data and /briefing for a briefing, but it does not explicitly say when to choose one route over another or when not to use the tool. The paid-per-call note and sample=true free preview provide useful selection context, but there is no explicit guidance for route choice or alternatives.

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?