Lilambd Data for Agents

science

World Science Output by Country and Field. The shape of world research in one API, counted from every record in OpenAlex (snapshot 2026-10-14, 464,765,485 works). Routes: /gaps (year, min_population, limit, offset); /rank (year, by, min_population, limit, offset); /fields (year, limit, offset); /rising (country, subfield, field, min_papers, sort, limit, offset); /subfields (q, limit, offset); /countries/{iso2} (from, to, limit, offset); /fields/{field_id} (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": "science"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /gaps, /rank, /fields, /rising, /subfields, /countries/{iso2}, /fields/{field_id}. 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 behavioral burden and does well: it discloses the paid x402 payment model, the exact per-call price, the data snapshot date and total record count, and that sample=true returns a free 3-row preview. It still omits rate limits, error behavior, and how many rows a paid call returns by default.

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 and front-loaded: purpose first, then the route list, then pricing and preview behavior. The semicolon-separated route list is efficient, though the long inline parameter enumeration makes it feel like a reference dump rather than 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 API with no output schema, the description explains inputs and billing but not what any route actually returns, what pagination defaults apply, or how errors are surfaced. It is adequate to start but incomplete for calling each route correctly.

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 describes a generic free-form params object; the description adds route-specific parameter lists (year, min_population, limit, offset; by; country, subfield, field, min_papers, sort; q; from/to). It does not explain what values parameters like 'by' or 'sort' accept, so it stops short of full semantic coverage.

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 a specific dataset and scope: world science output by country and field, built from OpenAlex works. That tells an agent exactly what resource this is and distinguishes it in content from sibling tools like japan or regions, though it never explicitly compares itself to them.

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 guidance is implicit in the route enumeration and in the cost note ('$0.005 USDC per call', 'sample=true for a free 3-row preview'), which tells an agent how to try it cheaply. There is no explicit when-to-use versus sibling tools guidance or when-not-to-use guidance.

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?