Lilambd Data for Agents

world-objects

World Objects. 228,881 world things (countries, cities, languages, scripts, calendars, festivals, currencies, firms with LEI, power plants, dishes, historic states, fictional planets marked FICTION) in one typed graph with 709,830 relations. Routes: /types; /objects (type, iso2, q, cell_05, limit, offset); /object/{id}; /neighbours/{id} (rel, type, limit, offset). Paid $0.01 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": "world-objects"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /types, /objects, /object/{id}, /neighbours/{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 5, 2026

TDQS

A3.5/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 disclose the most consequential behavior: every call costs $0.01 USDC via x402 with a _meta["x402/payment"] field, and sample=true yields a free 3-row preview. It also discloses the FICTION marker convention on fictional entries. It does not state rate limits, error/payment-failure behavior, or pagination semantics for limit/offset.

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 text is dense and front-loaded: what the data is, then routes with their parameters, then the payment/free-tier note. The long parenthetical inventory of entity types consumes meaningful space but does convey real coverage information. No filler sentences.

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 generic route-dispatch tool with no annotations and no output schema, the definition covers cost, routes, per-route parameters, and the free preview adequately. However, it never describes what an /object/{id} or /neighbours response looks like, what rel/type vocabularies are valid, or what cell_05 encodes, leaving an agent to guess at the shape of results and valid values.

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 the baseline would be 3, but the description adds real meaning beyond the schema by mapping each route to its accepted query parameters (/objects takes type, iso2, q, cell_05, limit, offset; /neighbours takes rel, type, limit, offset). It also explains that sample=true is a free 3-row preview rather than a normal pagination flag. It stops short of explaining cryptic parameters like cell_05 or the rel vocabulary.

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 defines the resource precisely: a typed graph of 228,881 world entities with 709,830 relations, enumerable types (countries, cities, LEI firms, dishes, FICTION planets), and four routes. This is clear enough to know it is a route-driven query surface over world data. It loses a point because it never differentiates from the many overlapping siblings (world-dishes, world-power, world-combine, regions, languages, calendars) that appear to expose slices of the same graph.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to choose this tool over world-dishes, world-power, regions, or any other sibling, nor any stated exclusions. The route list implies how to navigate (/types then /objects) and 'set sample=true for a free 3-row preview' implies a cheap trial pattern, but an agent receives no rule for tool selection.

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?