Skip to main content
Glama
Vessark

business-days-mcp

by Vessark

next_business_day

Calculate the next business day after a given date, with support for country-specific holidays and subdivisions.

Instructions

Find the first working day after a date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesCalendar date, YYYY-MM-DD.
countryNoISO 3166-1 alpha-2 country code. Defaults to US.
subdivisionNoOptional subdivision code, e.g. SCT.
Behavior2/5

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

No annotations provided. Description does not disclose behavior such as returning the same date if already a business day, handling of weekends/holidays, or the effect of country/subdivision parameters.

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?

Single sentence with no wasted words, but under-specified. Loses a point for missing critical context.

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

Completeness2/5

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

Given 3 parameters, localization support, and many sibling tools, the description is too brief. Lacks explanation of default holiday calendar, behavior for non-business days, and relationship to other tools.

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 baseline is 3. Description adds no extra information beyond what the schema already provides for each parameter.

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 verb 'Find', resource 'first working day', and constraint 'after a date'. It effectively distinguishes from sibling tools like 'previous_business_day' and 'is_business_day'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs siblings (e.g., when to use 'next_business_day' vs 'add_business_days'). No prerequisites or edge-case handling mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vessark/business-days-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server