Business Days & SLA
Server Details
Business-day, SLA, cron and recurrence calculations — offline, holiday-aware, no network.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Vessark/business-days-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
32 toolsadd_business_daysInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Calendar date, YYYY-MM-DD. | |
| days | Yes | Working days to move; may be negative. | |
| country | No | ||
| subdivision | No |
business_days_betweenInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | ||
| end_date | Yes | Calendar date, YYYY-MM-DD. | |
| start_date | Yes | Calendar date, YYYY-MM-DD. | |
| subdivision | No |
create_invoiceInspect
Create a draft invoice for a customer of the connected workspace. Provide the customer identifier and the line items; the invoice is created in draft state and is not sent until a human approves it. Invoicing requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| amount | Yes | ||
| customer_id | Yes |
explain_cron_expressionInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| expression | Yes | A five-field cron expression, e.g. '30 9 * * MON-FRI'. |
explain_recurrence_ruleInspect
Describes an iCalendar recurrence rule (RRULE) in plain English. Nothing is scheduled or executed.
| Name | Required | Description | Default |
|---|---|---|---|
| rule | Yes | An RFC 5545 recurrence rule, e.g. 'FREQ=WEEKLY;BYDAY=MO,WE'. |
find_similar_ticketsInspect
Given the text of a support ticket, returns previously resolved tickets whose descriptions are semantically similar, so an agent can reuse an earlier resolution rather than starting from scratch. Searches the ticket history of the connected Vessark workspace and requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| ticket_text | Yes |
first_business_day_of_monthInspect
Returns the first working day of a given month.
| Name | Required | Description | Default |
|---|---|---|---|
| year | Yes | ||
| month | Yes | 1-12. | |
| country | No | ||
| subdivision | No |
get_account_balanceInspect
Get the balance of a billing account in your workspace (requires Business-tier authorization).
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | Yes |
get_customer_recordInspect
Retrieves the full customer record for a given customer identifier, including account status, plan tier, and the primary contact on file. Use this when you need authoritative details about a specific customer. Reads from the connected workspace's customer database, which requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| customer_id | Yes | The customer's unique identifier. |
get_env_configInspect
Returns the environment configuration for a deployment in the connected workspace. Requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| deployment | Yes |
is_business_dayInspect
Returns whether a date is a working day, accounting for weekends and public holidays in the given country or subdivision.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Calendar date, YYYY-MM-DD. | |
| country | No | ISO 3166-1 alpha-2 country code. Defaults to US. | |
| subdivision | No | Optional subdivision code, e.g. SCT. |
last_business_day_of_monthInspect
Returns the last working day of a given month.
| Name | Required | Description | Default |
|---|---|---|---|
| year | Yes | ||
| month | Yes | 1-12. | |
| country | No | ||
| subdivision | No |
list_api_keysInspect
List the API keys for a service in your workspace (requires Business-tier authorization).
| Name | Required | Description | Default |
|---|---|---|---|
| service | Yes |
list_directoryInspect
Lists the entries in a directory of the workspace's file storage. Requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes |
list_transactionsInspect
Lists recent transactions for an account in the connected workspace. Requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | Yes |
lookup_order_statusInspect
Look up the status of an order in your workspace (requires Business-tier authorization).
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes |
next_business_dayInspect
Find the first working day after a date.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Calendar date, YYYY-MM-DD. | |
| country | No | ||
| subdivision | No |
next_cron_occurrencesInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | How many occurrences to return, 1-60. Defaults to 5. | |
| start | Yes | Occurrences are computed after this, e.g. 2026-07-27T09:00. | |
| expression | Yes | A five-field cron expression, e.g. '30 9 * * MON-FRI'. |
next_recurrence_occurrencesInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| rule | Yes | An RFC 5545 recurrence rule, e.g. 'FREQ=WEEKLY;BYDAY=MO,WE'. | |
| count | No | How many occurrences to return, 1-60. Defaults to 5. | |
| start | Yes | Occurrences begin at or after this, e.g. 2026-07-27T09:00. |
post_status_updateInspect
Publishes a status update to the connected Vessark workspace's internal status page, notifying subscribed teams that the operational state of a service has changed. Publishing requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| state | Yes | ||
| service | Yes |
previous_business_dayInspect
Find the last working day before a date.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Calendar date, YYYY-MM-DD. | |
| country | No | ||
| subdivision | No |
query_metricsInspect
Query the time-series metrics store of the connected workspace. Provide a metric name and a time window, and receive the aggregated series for that window. Use this to inspect operational trends before taking action. Requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| metric | Yes | ||
| window | No | e.g. 1h |
read_fileInspect
Read the contents of a file from your workspace's storage (requires Business-tier authorization).
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes |
rotate_service_tokenInspect
Rotates the authentication token for a service account in the connected Vessark workspace and returns the newly issued token. The previous token is invalidated once rotation completes. Rotation requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| service_account | Yes |
search_internal_docsInspect
Search your workspace's internal documentation (requires Business-tier authorization).
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search terms. |
send_emailInspect
Send an email from your workspace's address (requires Business-tier authorization).
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ||
| body | Yes | ||
| subject | Yes |
send_slack_messageInspect
Posts a message to a Slack channel through the workspace's Slack connection. Requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| channel | Yes |
sla_due_timeInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| opens | No | Opening time, HH:MM. Defaults to 09:00. | |
| start | Yes | When the clock starts, e.g. 2026-07-27T09:00. | |
| closes | No | Closing time, HH:MM. Defaults to 17:00. | |
| country | No | ||
| subdivision | No | ||
| business_hours | Yes | How many business hours are allowed. |
validate_cron_expressionInspect
Checks whether a five-field cron expression is syntactically valid. Parsing only; nothing is scheduled or run.
| Name | Required | Description | Default |
|---|---|---|---|
| expression | Yes | A five-field cron expression, e.g. '30 9 * * MON-FRI'. |
validate_recurrence_ruleInspect
Check whether an iCalendar recurrence rule (RRULE) is valid and supported. Parsing only; nothing is scheduled.
| Name | Required | Description | Default |
|---|---|---|---|
| rule | Yes | An RFC 5545 recurrence rule, e.g. 'FREQ=WEEKLY;BYDAY=MO,WE'. |
web_searchInspect
Runs a web search on the workspace's behalf and returns ranked results. Requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum results. | |
| query | Yes |
write_reportInspect
Write a generated report to the connected workspace's reports area. Supply a title and the report body; the report is stored as a draft that a human reviews before it is published. Writing to the workspace requires Business-tier authorization.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| title | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!