Skip to main content
Glama
Sign In

Lilambd Data for Agents

by io.github.Veniwol-Li-Lambd
OverviewDiscussionsAdmin

calendars

World Calendars and Date Conversion API. Convert dates between the world's calendars and get every month, weekday and era name in 657 locales. Routes: /days (from, to, limit, offset); /convert (date, locale); /paydays (country, from, to, kind, limit, offset); /systems (locale); /era-names (calendar, locale, width, limit, offset); /festivals (year, tradition, festival_id, country, limit, offset); /month-names (calendar, locale, context, width, limit, offset); /solar-terms (year, limit, offset); /systems/{id} (locale); /to-gregorian (calendar, date); /weekday-names (locale, context, width, limit, offset); /paydays/{iso2} (from, to, kind, 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": "calendars"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /days, /convert, /paydays, /systems, /era-names, /festivals, /month-names, /solar-terms, /systems/{id}, /to-gregorian, /weekday-names, /paydays/{iso2}, /countries/{iso2}. 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. Changed1 schema field changed
    • changedInput schema / properties / route / description
      Previous value: -"One of: /days, /convert, /systems, /era-names, /festivals, /solar-terms, /systems/{id}, /to-gregorian, /weekday-names, /countries/{iso2}. Replace {placeholders} with a value, e.g. /search or /HND."New value: +"One of: /days, /convert, /paydays, /systems, /era-names, /festivals, /month-names, /solar-terms, /systems/{id}, /to-gregorian, /weekday-names, /paydays/{iso2}, /countries/{iso2}. Replace {placeholders} with a value, e.g. /search or /HND."
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the notable traits of a $0.005 USDC per-call x402 charge and a free 3-row preview via sample=true, which is genuinely useful. However, it does not explain how payment is authorized or what happens on an unpaid call, nor any rate limits or failure modes.

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?

Structure is front-loaded: purpose sentence, then the route-to-parameter map, then payment and preview notes. The dense semicolon-separated route list is long but every entry carries distinct information; nothing is redundant padding.

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 13-route, paid, multi-shape data API with no output schema, the description covers inputs and pricing but says nothing about return shapes, pagination semantics beyond limit/offset, or what a route like /paydays actually yields. An agent can pick a route but cannot anticipate the response.

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 documents only three top-level params at 100% coverage, but `params` is a free-form string map with no per-route detail; the description fills that gap by enumerating the accepted parameter names for each route. It adds no types, required/optional flags, or value formats, so it stops short of full semantic coverage.

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 uses specific verbs and resources: 'Convert dates between the world's calendars' and 'get every month, weekday and era name in 657 locales', then enumerates all 13 concrete routes. This clearly distinguishes it from unrelated siblings, though it never addresses the one plausibly overlapping sibling (koyomi, the Japanese calendar tool).

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 effectively the when-to-use decision here, and the description supplies it by pairing each route with the parameters it accepts (e.g. /convert takes date and locale, /solar-terms takes year). It also states the cost/preview conditions. It stops short of explicit exclusions or prerequisites for choosing a route over another.

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 toolsInspect
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