Skip to main content
Glama
Sign In
Qiniso

Qiniso

Official
by qinisolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

next_holiday

Find the next public or bank holiday on or after a given date for over 200 countries. Use ISO country codes and optional subdivision to narrow results.

Instructions

USE THIS to find the next public/bank holiday on or after a date (default today) — e.g. to find the next working day. Supports ~200 countries (ISO code, e.g. GB, US, ZA, DE); subdivision narrows to a region.

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
countryNoISO country code (default GB), e.g. GB, US, ZA, DE.
afterNoFind the next holiday on/after this date (YYYY-MM-DD); default today.
subdivNoSubdivision code (e.g. UK nation SCT/WLS/NIR, or a US state).

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?

With no annotations, the description carries the full burden. It discloses the supported countries and subdivision narrowing, but omits details on error handling (e.g., no holiday found), return format, or whether it accounts for weekends. The behavior is adequately described for common use cases.

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 two sentences with no extraneous text. It opens with the primary purpose ('USE THIS to find...') and immediately provides an example, making it highly efficient and easy to parse.

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?

Given no annotations or output schema, the description covers the main purpose and parameters but lacks details on return value (e.g., date string vs. object) and edge cases (e.g., no holiday found). This leaves some ambiguity for the agent.

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 description largely echoes schema fields (e.g., default GB, YYYY-MM-DD format). It adds minor value with examples and context (e.g., 'e.g. GB, US, ZA, DE') but does not provide significant additional meaning beyond the input schema.

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 clearly states the action (find) and resource (next public/bank holiday), with specific examples like 'find the next working day'. It distinguishes itself from sibling tools like is_holiday by focusing on finding the next holiday rather than 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?

The description explicitly advises when to use this tool ('USE THIS to find the next public/bank holiday') and provides a practical example. While it does not explicitly state when not to use it or reference alternatives, the context is sufficient for an agent to infer appropriate usage.

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