Lilambd Data for Agents

marketplaces

Lilambd World Marketplaces Physical and Digital API. Where the world buys and sells, in one shape: 409,266 physical market places in 228 countries (199,888 shopping malls, 64,192 farmers' markets, 31,899 flea markets, 20,775 auction houses, 11,238 bazaars and souks, 5,173 night markets, 3,609 fish markets, wholesale markets, hawker centres and more) with coordinates, region, town, website and a locality class (big city, city, regional, remote: 29,146 places over 100 km from any 100k+ city), plus 5,457 digital marketplaces and app stores. Nearby search, country and region views, rankings, coverage gaps and a one-call country profile. Sources: Overture Maps places 2026-10-21.0 (CDLA-Permissive-2.0 / Apache-2.0 / CC0 rows only) and Wikidata (CC0). Compiled by Lilambd. Routes: /gaps (min_population, limit, offset); /rank (kind, by, limit, offset); /kinds; /nearby (lat*, lon*, radius_km, kind, limit, offset); /places (country, kind, locality_class, q, region, town, limit, offset); /digital (q, country, kinds, deal_type, limit, offset); /countries (sort, limit, offset); /places/{id}; /digital/{id}; /admin1/{iso2} (limit, offset); /countries/{iso2}. 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": "marketplaces"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /gaps, /rank, /kinds, /nearby, /places, /digital, /countries, /places/{id}, /digital/{id}, /admin1/{iso2}, /countries/{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 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description does the heavy lifting and does disclose key behavior: paid access at $0.005 USDC per call via x402 in _meta["x402/payment"], plus a free sample=true preview capped at 3 rows, and data provenance/freshness (Overture 2026-10-21.0, Wikidata). It stops short of describing return payload shape, error behavior or pagination semantics beyond passing 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and the routes, but padded with marketing phrasing ('Where the world buys and sells, in one shape') and a long statistics dump (199,888 shopping malls, 64,192 farmers' markets, ...). The counts build confidence in coverage but cost a lot of tokens for little call-time value.

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 multi-route paid aggregator with no output schema, the description covers payment mechanics, the free preview escape hatch, source attribution and the route-to-parameter map. Return value structure and pagination/rate-limit behavior are the notable omissions.

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% and the schema only says route is 'one of' a list, so the description adds real value by pairing each route with its accepted parameters (e.g. /nearby needs lat*, lon*, radius_km, kind; /places takes country, kind, locality_class, q, region, town). That mapping is the difference between a usable and unusable call for this multiplexer.

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?

States a specific resource (physical and digital marketplaces with coordinates, region, town, locality class) and enumerates the exact routes it exposes. It never names the obvious sibling (local-markets) or explains how it differs, so an agent still has to guess between the two marketplace-shaped tools.

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 implicitly tells an agent which route serves which intent (nearby search, country view, rankings, gaps, digital marketplaces), which is useful, but there is no explicit when-to-use/when-not guidance relative to siblings such as local-markets, place-brief or regions.

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?