Skip to main content
Glama

Lilambd Data for Agents

occupation-pay-ladder

What does each occupation earn per hour in a country, how many people do it, and how does that pay compare abroad?. ILOSTAT hourly earnings for the ISCO-08 major groups (local currency, USD, PPP) joined with employment by occupation: pay index vs the national average, employment share, and a PPP comparison of one occupation across up to 10 countries. Computed by Lilambd. Routes: /answer (country*, occupation, compare, limit); /countries (limit). 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": "occupation-pay-ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /answer, /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

A4.3/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 and does disclose the most consequential trait: it costs $0.5 USDC per call via x402 and sample=true yields a free 3-row preview, which directly affects how an agent should call it. Gaps remain on data recency/coverage years, error behavior for unsupported countries, and rate limits.

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 leads with the user-facing question, then layers data sources, outputs, routes, and payment in a sensible order with no rambling. It is dense and slightly overpacked into two long sentences, and the 'Computed by Lilambd' attribution adds little, but nearly every clause is load-bearing.

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?

There is no output schema, yet the description enumerates the returned metrics (pay index, employment share, PPP comparison) and the route/parameter contract, plus payment and preview behavior. Coverage of temporal scope and failure modes is absent, which is the main remaining hole for a paid data tool.

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?

The schema's params object is a generic string map, so the schema itself explains very little; the description compensates by naming the actual parameter keys (country*, occupation, compare, limit) per route and noting the 10-country cap on comparison. The asterisk on country is unexplained and compare/limit semantics are only partially described, keeping it below a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb-and-resource combination: hourly earnings by occupation (ILOSTAT, ISCO-08 major groups) joined with employment counts, plus a cross-country PPP comparison. It specifies the source data, the currency variants (local, USD, PPP), and the derived metrics (pay index vs national average, employment share), so an agent knows exactly what question this tool answers.

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

Usage Guidelines4/5

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

Route selection is spelled out ( /answer vs /countries ) with the parameters each accepts, and the free sample path is explicitly offered as a preview option. What is missing is any when-not-to-use guidance or explicit steering away from a related tool, though no obviously competing sibling is named in the provided context.

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