Skip to main content
Glama

Tool catalogue

catalogue
Read-onlyIdempotent

Every tool across all Data Butler servers (UK rates; UK exams; provenance; exact statistics; vehicles: UK MOT, UK, French and Japanese recalls; take-home pay for ten countries; software support status and end-of-life timelines for 14 runtimes and operating systems; central-bank policy rates: Bank of England, Fed, ECB; US federal rates and thresholds (us_rates_lookup: income tax, Social Security, Medicare, retirement, HSA, estate and gift, capital gains, IRMAA, RMD); German tax and social-insurance figures (de_rates_lookup: Einkommensteuertarif, Sozialversicherung, Mindestlohn, Minijob, Kindergeld, Kinderfreibetrag, Pauschbeträge, Entfernungspauschale, Umsatzsteuer); UK vehicle tax (VED) and MOT rules; UK exam dates and spec changes: results days, the summer 2027 timetable, entry deadlines, new specifications; calendar facts: public holidays, tax-year starts and daylight-saving switches for 2026–2028; UK government services: passport, driving licence, vehicle tax/SORN, voting, birth/death registration, Blue Badge, Self Assessment, NI number, Universal Credit, EU Settlement Scheme, eVisa, ETA; Japan vehicle statutory costs (jp_vehicle_costs_lookup: 自動車重量税, エコカー減税, 自賠責保険, 検査手数料, 自動車税, 軽自動車税); Japan daily-life official figures (jp_living_costs_lookup: 最低賃金, 健康保険料率, 年金, 雇用保険, 児童手当, 高額療養費, 祝日, 消費税, 基礎控除, 住民税); UK inflation: CPI and CPIH 12-month rates, CPI index and annual averages (ONS); US inflation (us_inflation_lookup: BLS CPI-U 12-month rate, index level, annual averages)), with input schemas — including tools not listed at this front door. Optional query filters by keyword. Run any of them with call, or connect to serverUrl directly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "catalogue"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNokeyword filter, e.g. regression, exam, npm

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful context that the catalogue includes tools not listed at this front door, but says nothing about result size, pagination, or how much detail each entry returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The middle of the description is a single enormous parenthetical enumerating dozens of sub-tool names and foreign-language field terms — largely redundant with what the catalogue itself returns. The opening clause is well front-loaded, but the body reads as keyword stuffing rather than structure.

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 zero-required-parameter read-only listing tool, the description is more than sufficient and notes that results include input schemas. It would be stronger if it indicated roughly how many tools are returned or the entry format, since there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single query parameter is documented in the schema with an example. The description only restates 'Optional query filters by keyword', adding no syntax, matching behavior, or empty-result semantics beyond the schema.

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 opens by stating it enumerates every tool across all Data Butler servers with input schemas, and the parenthetical enumerates the domains covered. It doesn't differentiate itself from siblings like coverage or domain_provenance, which could plausibly also serve discovery needs.

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 explicitly routes the agent: discover here, then 'Run any of them with call, or connect to serverUrl directly,' which names the alternative path. It stops short of saying when to prefer coverage or domain_provenance over this 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.