Skip to main content
Glama
Sign In
localecheck

localecheck

by qinisolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

next_holiday

Find the next public or bank holiday occurring on or after a given date. Supports GB and US, including UK nations and US states, to help you determine the next holiday or plan a working day.

Instructions

Find the next public/bank holiday on or after a date (default today). USE THIS to answer 'when is the next holiday' or find the next working day. Country is GB or US; subdiv narrows to a UK nation or US state.

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_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoGB
afterNo
subdivNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the behavior of finding the next holiday on/after a date with default today, and mentions country/subdivision options. But it does not specify output format (e.g., what is returned) or potential side effects. This is adequate but lacks some behavioral context.

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 concise sentences that front-load the purpose and use case, then provide parameter details. No redundant information.

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?

No output schema exists, so description should explain return value. It does not mention what the tool returns (e.g., date, name, object). Given the complexity (3 optional parameters) and sibling tools, this omission makes it less complete.

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 0%, so description must compensate. It explains 'country is GB or US' and 'subdiv narrows to a UK nation or US state', adding meaning. However, the 'after' parameter is only implied via 'on or after a date (default today)' without specifying format or constraints, leaving some ambiguity.

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?

Description clearly states 'Find the next public/bank holiday on or after a date' with verb 'find' and resource 'next public/bank holiday'. It implies differentiation from sibling 'is_holiday' by specifying use for 'next holiday' vs checking a specific date.

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?

Explicitly states 'USE THIS to answer when is the next holiday or find the next working day', providing clear context. However, it does not explicitly state when not to use it or mention alternatives like 'is_holiday'.

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

Deploy Server

Other Tools