Skip to main content
Glama

Calcgrid

by com.tttkmbb
OverviewDiscussionsAdmin

UK Working Day Checker

check_uk_working_day
Read-onlyIdempotent

Use this when you need to know whether a 2024-2028 UK date is a Monday-Friday working day after applying the official bank holidays for the selected division. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery.

Do not use this when you need a local council, school, employer, financial-market, emergency-closure or non-UK calendar, or a date outside 2024-2028. What it computes: Checks whether a date is a normal working day in England and Wales, Scotland or Northern Ireland using a pinned snapshot of the official GOV.UK bank-holiday feed. Example user requests: Is 28 December 2026 a working day in England and Wales, or the Boxing Day substitute holiday? | Is Scotland working on 15 June 2026? | Check whether 13 July 2026 is a working day in Northern Ireland. Inputs: date (date); division (enum, optional). Complete JSON argument examples: {"date":"2026-12-28","division":"england-and-wales"} | {"date":"2026-06-15","division":"scotland"} Outputs: date, weekday, division, division_name, is_working_day, day_type, bank_holiday_name, bank_holiday_notes, status_basis, source_url, licence, dataset_version, coverage_start, coverage_end, source_snapshot_sha256. Formula: official bank-holiday event → non-working; else Saturday/Sunday → non-working; else Monday-Friday → working Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uk-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uk-working-day.md

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesUK civil date in YYYY-MM-DD format, within 2024-2028.
divisionNoGOV.UK bank-holiday division. England and Wales share one official list; Scotland and Northern Ireland have separate lists.england-and-wales

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksNo
resultYes
requestYes
sourcesNo
successYes
versionNo
freshnessNo
timestampYes
next_actionsNo
service_versionYesDeployed Calcgrid implementation version used for the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / service_version
      Added value: +{
+  "description": "Deployed Calcgrid implementation version used for the result.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "success",
-  "request",
-  "result",
-  "timestamp"
-]New value: +[
+  "success",
+  "service_version",
+  "request",
+  "result",
+  "timestamp"
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare readOnlyHint and idempotentHint, and the description adds substantial behavioral context: the exact formula, the use of a pinned GOV.UK snapshot, the supported divisions, and the output fields. This goes well beyond what the annotations alone provide and accurately describes the tool's computation and data provenance.

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?

The description is dense but well-organized, with clear sections for use cases, exclusions, inputs, outputs, formula, and fallback. Every sentence adds practical value, from the working-day formula to the REST fallback and documentation link. It is front-loaded with the primary use and exits early, with no tautology or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the two simple parameters, the existing output schema, and the annotations, the description is highly complete. It explains the date range, division-specific behavior, formula, data source, snapshot versioning, and fallback invocation. An agent has everything needed to select, invoke, and interpret the result correctly.

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 the schema already fully documents date and division, including formats, enum values, defaults, and examples. The description mostly restates these facts in prose and examples rather than adding new semantic meaning, so the baseline of 3 is appropriate.

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 states a specific verb and resource: checking whether a 2024-2028 UK date is a Monday-Friday working day after applying bank holidays for a division. It also differentiates itself from related tools like add_uk_working_days and count_uk_working_days by focusing on a single date check and by instructing the agent to call the tool directly rather than deriving the answer.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool ('Use this when you need to know whether...') and when not to use it ('Do not use this when you need a local council, school, employer...'), including clear exclusions for non-UK calendars and dates outside 2024-2028. It even provides a direct REST fallback and tells the agent not to guess other API paths, giving strong selection guidance.

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

All Calcgrid toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources