Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Bank holidays

bank_holidays
Read-onlyIdempotent

Retrieve upcoming official UK public holidays by region to plan payments and bills that shift around weekends or holidays.

Instructions

Upcoming UK bank holidays (official gov.uk list, bundled) for England and Wales, Scotland or Northern Ireland. Useful because pay due on a bank holiday or weekend usually arrives the working day before, and payments due then are usually taken the next 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": "bank_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow far ahead (default 120 days)
regionNoDefault: england-and-wales, or LIFE_ADMIN_REGION

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/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 meaningful context beyond that: the data is bundled/official rather than fetched live, and the reason the results matter is date-shifting of payments. It stops short of saying whether the bundled list can be stale or how far it extends beyond the requested window.

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

Conciseness5/5

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

Two sentences with no filler: the first front-loads what is returned and its regional scope, the second justifies why it matters. Nothing is repeated from the schema and nothing could be cut without losing information.

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 two-parameter, zero-required, read-only lookup with full schema coverage and annotations, this is nearly complete. The one remaining gap is that no output schema exists and the description never hints at the return shape (dates with holiday names per region), which an agent must discover by calling it.

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 description coverage is 100%, so both `days` (default 120, max 800) and `region` (enum with a LIFE_ADMIN_REGION default) are already fully documented. The description only restates the region options and the notion of 'upcoming', adding no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 names a specific resource (UK bank holidays), its source (official gov.uk list, bundled) and its scope (England and Wales, Scotland or Northern Ireland), which maps directly to the region enum. No sibling tool in the list touches holiday calendars, so the purpose is unambiguous at a glance.

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 second sentence supplies a clear application context: it is called to reason about payment timing, since money due on a holiday or weekend typically moves to the adjacent working day. It does not name an alternative or state exclusions, but no sibling overlaps in behavior, so the implied usage is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.