Skip to main content
Glama

Coverage

coverage
Read-onlyIdempotent

Exactly what Data Butler covers and does not, per area, including figures it does not serve yet. Areas: uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process, jp-vehicle-costs, jp-living-costs, uk-inflation, us-inflation (omit for all). Returns rate categories and tax years, boards/subjects, package ecosystems, stats operations, vehicle datasets, take-home-pay countries, the 14 software products with end-of-life data, central-bank policy rates (boe, fed, ecb), US federal rate categories and tax year, German rate categories and Veranlagungszeitraum, UK vehicle tax (VED) and MOT rule categories, UK exam dates (results, timetable, deadlines, spec-changes for jcq, aqa, pearson, ocr, wjec-eduqas; sqa results day), calendar facts: public holidays (uk, us, de, fr), tax years and daylight saving (uk, us, de, fr, au, in, ca, br, pl) for 2026–2028, UK government services (passports, DVLA, voting, registrations, Self Assessment, benefits, eVisa, ETA), Japanese vehicle statutory cost categories (weight tax, 自賠責, inspection fees, car taxes), Japanese daily-life figure categories (minimum wage, health insurance, pension, employment insurance, benefits, holidays, consumption tax, income tax, resident tax), UK inflation categories (cpi, cpih), US CPI-U inflation (latest month, prior month, annual averages), and an explicit notCovered list.

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": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoone of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process, jp-vehicle-costs, jp-living-costs, uk-inflation, us-inflation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"one of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process, jp-vehicle-costs, jp-living-costs"New value: +"one of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process, jp-vehicle-costs, jp-living-costs, uk-inflation, us-inflation"
  2. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"one of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process, jp-vehicle-costs"New value: +"one of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process, jp-vehicle-costs, jp-living-costs"
  3. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"one of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process"New value: +"one of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process, jp-vehicle-costs"
  4. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"one of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar"New value: +"one of uk-rates, uk-exams, provenance, stats, vehicles, tax, software-eol, policy-rates, us-rates, de-rates, uk-vehicle-rules, uk-exam-dates, calendar, uk-gov-process"
  5. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it promises an explicit notCovered list and spells out the categories of content an agent will receive per area. It does not describe response shape or size, which is minor for a static introspection tool.

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 purpose is front-loaded, but the description then becomes a single enormous run-on sentence that re-lists the area enum already fully present in the schema before dumping an unstructured catalogue of return contents. A table or short summary would carry the same information far more efficiently.

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 one-parameter, no-required-args introspection tool with no output schema, the description is complete enough: it covers the purpose, the optional area filter, the areas, and the returned content categories. Only the exact response structure (field names/shape) is left implicit.

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% and the schema enumerates the valid area values, so the baseline is a 3. The description goes further by glossing what each area actually yields (e.g. policy rates cover boe/fed/ecb; uk-exam-dates covers jcq/aqa/pearson/ocr/wjec-eduqas), which meaningfully enriches area selection beyond the raw enum.

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 first sentence states a specific purpose: it enumerates what "Data Butler" covers and does not cover, per area, plus a notCovered list. It is clearly a coverage/introspection tool, distinguishable from siblings like get_fact or catalogue. It does not explicitly differentiate itself from catalogue or domain_provenance, so it falls just short of a 5.

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

Usage Guidelines3/5

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

The only usage guidance is the parenthetical "(omit for all)" for the area parameter, which is helpful for the optional-parameter case. There is no statement of when to reach for this tool versus catalogue/domain_provenance/what_changed_since, so choosing between the metadata siblings still requires inference.

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.