Skip to main content
Glama

Lilambd Data for Agents

wage-hours

How many minutes of work does it take in a country to earn the world price of a commodity?. Joins ILOSTAT mean hourly earnings (USD, by ISCO occupation) with World Bank Pink Sheet commodity prices for the same year. Returns minutes of work per unit (kg, barrel, troy oz, tonne), units per hour of work, history and the spread across occupations. Computed by Lilambd. Routes: /items (limit); /answer (country*, item*, occupation, 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": "wage-hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /items, /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 burden and does well: it discloses the payment mechanism and cost ($0.5 USDC per call via x402 in _meta["x402/payment"]), the free-sample escape hatch, data provenance, and the shape of results (minutes per unit, units per hour, history, occupational spread). It does not cover failure modes, caching, or what an invalid route returns.

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 core computation and data sources are front-loaded in the opening two sentences, then results, then routing and pricing; no sentence is filler, though the routing list is compact to the point of terseness and the pricing/sample note is buried at the end.

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 tool with a nested open-ended params object, no annotations, and no output schema, the description covers purpose, sources, return shape, routes, and cost. The remaining gaps are edge-case behavior (invalid route, unknown country/item) and exact code formats, which a caller would have to discover empirically.

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 schema already documents route, params, and sample; the description still adds real meaning by specifying which parameters belong to which route and marking country and item as required for /answer. It does not clarify the accepted value formats for country or item codes beyond the asterisk convention.

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 the exact computation (minutes of work to earn a commodity's world price), the two joined data sources (ILOSTAT mean hourly earnings by ISCO occupation, World Bank Pink Sheet prices), and the output dimensions, so an agent can tell this apart from a plain prices or units tool without opening the schema.

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?

It gives concrete routing guidance, mapping each of the three routes to the parameters they accept (e.g. /answer with country*, item*, occupation, limit), and tells the agent to use sample=true for a free 3-row preview before paying. It stops short of naming when to prefer this over its siblings or any when-not case.

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