Skip to main content
Glama

next_bank_holidays

FREE. Next 3 UK bank holidays for a nation, plus whether today is a working day.

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

Input Schema

NameRequiredDescriptionDefault
regionNoengland (default), wales, scotland, northern-ireland

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?

No annotations are supplied, so the description carries the full burden. It does disclose cost ("FREE") and the shape of the result (next 3 holidays plus today's working-day status), but says nothing about auth, rate limits, or how the holiday data is returned. For a simple read-only lookup that is a moderate but not severe gap.

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?

One short sentence, front-loaded with the cost signal and then the payload. Nothing is padded, though "FREE." as a fragment is slightly cryptic without explanation.

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?

A simple single-parameter read tool with no output schema; the description states what it returns and that the region defaults. An agent has enough to call it correctly, with only minor gaps around return format.

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 region parameter already enumerates england/wales/scotland/northern-ireland with a stated default. The description only implies the region via "for a nation," adding little beyond the schema. Baseline 3 is appropriate.

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?

States a specific resource and scope: the next 3 UK bank holidays for a chosen nation, plus a working-day flag. An agent knows exactly what data comes back. It does not explicitly distinguish itself from the sibling working_days, which likely overlaps on the working-day portion.

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?

Usage is implied by the content (UK bank holidays by region, working-day check), but there is no explicit when-to-use or when-not-to-use guidance. The sibling working_days tool plausibly covers related ground and the description never routes the agent between them.

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.