Skip to main content
Glama

Lilambd Data for Agents

cit-rate-changes

Which countries raised or cut their corporate tax rate between two years, and where does a country rank now?. Compares OECD statutory combined corporate income tax rates across ~146 jurisdictions between two years: who raised, who cut, by how many points, the median shift, and optionally one country's rank and year-by-year path. Computed by Lilambd. Not tax advice. Routes: /years (limit); /answer (from*, to, direction, country, 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": "cit-rate-changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /years, /answer. 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 discloses important behavior: pricing at $0.5 USDC per call via x402, a free 3-row preview via sample=true, the data source, and a not-tax-advice disclaimer. It does not cover rate limits, error behavior, or full authentication details beyond payment, leaving some gaps.

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 description is front-loaded with the core question and then supplies scope, routing, payment, and preview details. It is generally efficient, though the first sentence and the opening of the second overlap in stating who raised or cut rates, and the stray '?.' is slightly awkward.

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 tool with no annotations and no output schema, the description does a good job explaining outputs, pricing, preview behavior, and route options. It still leaves some parameter value constraints unspecified, but the core information an agent needs to select and invoke the tool is present.

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, but the description adds meaningful detail beyond the generic schema by naming the route-specific parameters: /years takes limit, and /answer takes from*, to, direction, country, and limit. It still does not define accepted direction values, country identifier format, or limit bounds, so the added semantics are helpful but incomplete.

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 states a specific verb and resource: it compares OECD statutory combined corporate income tax rates across about 146 jurisdictions between two years, identifying who raised or cut rates and by how much. It also clarifies optional country rank and year-by-year path outputs, so an agent can immediately tell what the tool does.

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?

The description gives clear context for when the tool is appropriate: comparing corporate tax rate changes between two years and optionally retrieving one country's rank and trajectory. It does not explicitly name alternatives or state when not to use it, but the scope is sufficiently clear for this specialized tool.

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