business-days-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| is_business_dayA | Returns whether a date is a working day, accounting for weekends and public holidays in the given country or subdivision. |
| next_business_dayB | Find the first working day after a date. |
| previous_business_dayB | Find the last working day before a date. |
| add_business_daysA | Move a number of working days forward or backward from a date, skipping weekends and public holidays. Use a negative number to count backwards. Zero returns the date unchanged. |
| business_days_betweenA | Counts the working days between two dates, excluding weekends and public holidays. The range is half-open — the start date counts and the end date does not — so Monday to Tuesday is one working day. The result is negative when the end precedes the start. |
| first_business_day_of_monthC | Returns the first working day of a given month. |
| last_business_day_of_monthB | Returns the last working day of a given month. |
| sla_due_timeA | Works out when a service-level agreement falls due, counting only business hours on working days. If the clock starts outside business hours it waits until the next working day opens. Business hours default to 09:00-17:00 and times are wall-clock in the calendar's own locality. |
| validate_cron_expressionA | Checks whether a five-field cron expression is syntactically valid. Parsing only; nothing is scheduled or run. |
| explain_cron_expressionA | Translate a five-field cron expression into plain English. Supports ranges, lists, steps, and month or weekday names. This describes the expression; it never schedules or executes anything. |
| next_cron_occurrencesA | Computes when a five-field cron expression would next fire after a given start time, returning up to 60 timestamps. A pure calculation over the expression: no job is created, stored, or executed. |
| validate_recurrence_ruleA | Check whether an iCalendar recurrence rule (RRULE) is valid and supported. Parsing only; nothing is scheduled. |
| explain_recurrence_ruleA | Describes an iCalendar recurrence rule (RRULE) in plain English. Nothing is scheduled or executed. |
| next_recurrence_occurrencesA | Expand an iCalendar recurrence rule (RRULE) into its next occurrences from a start date and time, honouring INTERVAL, COUNT, UNTIL, BYDAY, BYMONTHDAY, and BYMONTH. A pure calculation: it creates no schedule, stores nothing, and runs nothing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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