Skip to main content
Glama

Lilambd Data for Agents

protected-areas

How much of a country is inside mapped protected areas, and how close is nature to a big city?. Protected share of land per country (OpenStreetMap protected-area polygons, overlaps counted once) with counts of World Heritage, Ramsar, biosphere reserve, UNESCO Global Geopark and national park designations from Wikidata; plus a nature access score for the 120 largest cities. Not derived from WDPA. Routes: /; /answer (country, city); /cities (country, limit, offset); /countries (limit, offset, order). Paid $0.5 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": "protected-areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /, /answer, /cities, /countries. Replace {placeholders} with a value, e.g. /search or /HND.
paramsNoQuery parameters, e.g. {"q":"tokyo","limit":"50"}
sampleNoFree preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses data provenance and overlap handling, the paid-access model ($0.5 USDC per call via x402 `_meta["x402/payment"]`), and a concrete free escape hatch (sample=true, 3 rows). Gaps remain on error behavior, rate limits, and response shape, but the cost/auth disclosure is the critical piece an agent needs before invoking a paid endpoint.

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?

It is front-loaded with the user-facing question, then scope/provenance, then routes, then pricing and the free-preview escape hatch — a sensible order with no filler sentences. Minor cost: a stray '?.' punctuation error and a dense second sentence that packs three datasets together.

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?

With no output schema and no annotations, the description supplies the essentials an agent needs: what is measured, which sources, how routes map to params, what it costs, and how to preview cheaply. Remaining gaps (accepted formats for country/city identifiers, response field names, failure modes) are real but secondary for a read-only data endpoint.

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 is 3; the description earns above baseline by mapping each route to the parameters it consumes (country/city for /answer, country/limit/offset for /cities, limit/offset/order for /countries). This is meaningfully more than the schema's bare 'One of: /, /answer, /cities, /countries', though it still doesn't specify value formats such as country-code style for the 'country' argument.

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 specific resource and its two outputs: protected-area land share per country (OSM polygons, overlaps counted once) and a nature access score for the 120 largest cities, including which designation counts come from Wikidata and an explicit 'Not derived from WDPA' provenance note. This clearly separates it from generic siblings like 'land' or 'biodiversity', though no sibling is named as an alternative.

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 only implied: the route list ('/answer (country, city); /cities (country, limit, offset); /countries (limit, offset, order)') hints at which endpoint serves which need, but there is no explicit statement of when to pick this tool over another or when not to. An agent can infer country-level vs city-level use from the route parentheticals, but must do the work itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources