Skip to main content
Glama

Call any tool

call
Read-onlyIdempotent

Run any Data Butler tool by name — the long tail not listed here: exam_spec_lookup, exam_paper_index; exact statistics (distribution, hypothesis_test, confidence_interval, bayes_update, linear_regression, descriptive_stats); the vehicles hub (uk_mot_reliability, uk_recalls_for_model, uk_recalls_search, fr_recalls_for_model, fr_recalls_search, jp_recalls_for_model, jp_complaints_summary); software end-of-life (support_status {product, version}, support_timeline {product} for nodejs, python, ubuntu, debian, android, ios, macos, windows, oracle-jdk, go, ruby, php, postgresql, react); policy_rate (Bank of England Bank Rate, Fed federal funds target range, ECB key rates — committed data verified against the banks' own pages); us_rates_lookup (US federal rates and thresholds for the current tax year: income-tax, social-security, medicare, retirement, hsa, estate-gift, social-security-benefits, medicare-costs, capital-gains); de_rates_lookup (German tax and social-insurance figures for the current Veranlagungszeitraum: income-tax, social-insurance, minimum-wage, minijob, kindergeld, kinderfreibetrag, sparer-pauschbetrag, arbeitnehmer-pauschbetrag, entfernungspauschale, vat); uk_vehicle_rules_lookup (UK car tax: first-year CO2 bands, standard rate, expensive car supplement, 2001–2017 bands, pre-2001 rates, electric cars, historic vehicles; MOT due dates, fees, retests, penalties — verified against gov.uk); UK exam dates (uk_exam_dates {kind: results|timetable|deadlines|spec-changes, board?, qualification?}); calendar facts (calendar_facts {country, kind: holidays|tax-year|dst, year?, region?} and next_holiday {country, from?} — holidays for uk, us, de, fr; tax years and DST for uk, us, de, fr, au, in, ca, br, pl; 2026–2028); uk_gov_process (UK government services — passport and ETA fees, driving licence renewal, SORN, register to vote, birth/death registration, Self Assessment deadlines, NI number, Universal Credit, EU Settlement Scheme, eVisa — fees, processing times, start URLs, dated changes, verified against gov.uk); jp_vehicle_costs_lookup (Japan 車検 statutory costs and car taxes: weight-tax, weight-tax-eco, cali, inspection-fee, auto-tax, kei-tax — verified against MLIT, FSA, NALTEC and local-government pages); jp_living_costs_lookup (Japan minimum wage by prefecture, 協会けんぽ rates, pensions, employment insurance, benefits, 2027 holidays, consumption tax, income-tax deductions, resident tax — verified against MHLW, NTA, 総務省, 内閣府, こども家庭庁, 日本年金機構 and 協会けんぽ pages); uk_inflation_lookup (UK CPI and CPIH inflation from the ONS); us_inflation_lookup (US CPI-U from the BLS: 12-month percent change, index level 1982-84=100, annual averages from 2021, with release dates). uk_rates_lookup, domain_provenance, package_provenance and take_home_pay are listed directly. See catalogue for schemas. The result carries the inner tool's freshness and cite.

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": {
      "tool": "<tool>"
    },
    "name": "call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYestool name from catalogue
argumentsNothat tool's arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact — 'The result carries the inner tool's freshness and cite' — plus per-domain provenance claims (verified against gov.uk, ONS, BLS, etc.). It says nothing about failure modes for an unrecognized tool name, argument validation, or whether dispatch can recurse.

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 key rule is front-loaded, but the body is a single enormous sentence-pile of dozens of tool names in nested parentheses that is hard to scan. A sibling `catalogue` tool exists precisely for discovery, so much of this enumeration duplicates it and dilutes the routing instruction.

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?

The description conveys that results carry freshness and citation and that schemas live in the catalogue, which covers the essentials for a dispatcher with no output schema. For a tool with nested `arguments` and openWorld dispatch, it is still thin on error behavior and on how strictly inner arguments are validated.

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% for both parameters, so the baseline is 3. The description does add real value by pointing at the catalogue as the source of the inner tool's name and argument schema, which is the central semantic problem for a dispatcher. But it gives no shape for `arguments` beyond the schema's one-liner.

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 opening clause states a specific verb and resource ('Run any Data Butler tool by name') and qualifies scope as 'the long tail not listed here'. It also names which related tools are exposed directly (uk_rates_lookup, domain_provenance, package_provenance, take_home_pay), so the agent can tell it apart from siblings. The rest of the description is an enumeration of inner tools rather than further purpose statement.

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 long tail not listed here' plus the list of directly-exposed tools gives a clear selection rule. It also routes the agent to the catalogue for schemas. It stops short of an explicit exclusion (e.g. 'never use this for tools listed directly') or guidance on what to do when a name is unknown.

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.