Deterministic date math agents get wrong, done in code over MCP: business_days adds and counts working days with holiday awareness, meeting_overlap finds shared windows across UTC offsets including half-hour zones, recurrence_expand generates concrete dates, with deadline_planner and sla_due in the premium tier. Every failure mode returns a structured error.
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.
Score is being calculated. Check back soon.
business_daysBusiness DaysDo business-day math that skips weekends and your holiday list. FREE.
Either add N business days to start_date (set add_days), or count the business days between start_date and end_date (set end_date). Typical input {"start_date": "2026-03-02", "add_days": 10} returns {"result_date": "2026-03-16", "result_weekday": "Monday", ...}; with end_date set it returns {"business_days_between": N, "from": ..., "to": ...}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "dates must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| add_days | No | Business days to add; negative subtracts. Range -5000 to 5000. Ignored when end_date is provided. | |
| end_date | No | Optional end date, ISO YYYY-MM-DD. When set, the tool counts business days between start_date and end_date instead of adding. | |
| holidays | No | Optional list of ISO YYYY-MM-DD dates to treat as non-working days, e.g. ["2026-12-25"]. | |
| start_date | Yes | Anchor date in ISO format YYYY-MM-DD, e.g. "2026-03-02". |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
deadline_plannerDeadline PlannerPlan a task schedule backward from a hard deadline in business days. PREMIUM (license).
Given ordered tasks with business-day durations, returns each task's start/end dates, the latest safe start, and slack from today. Typical input {"due_date": "2026-06-01", "tasks": [{"name": "Draft", "days": 3}, {"name": "Review", "days": 2}]} returns {"schedule": [...], "latest_safe_start": "YYYY-MM-DD", "slack_business_days_from_today": N, "verdict": "..."}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "due_date must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| tasks | Yes | Ordered list of task objects, each {"name": str, "days": int} where days is the business-day duration (1-365); the first 30 tasks are scheduled. | |
| due_date | Yes | The deadline, ISO YYYY-MM-DD. | |
| holidays | No | Optional list of ISO YYYY-MM-DD dates treated as non-working days. | |
| buffer_days | No | Business days of safety margin kept free before due_date, clamped to 0-365. Default 1. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
meeting_overlapMeeting OverlapFind the shared meeting window across time zones inside working hours. FREE.
Give one UTC offset per participant and an optional working-hours window. Typical input {"offsets_utc": [-8, 1, 5.5]} returns {"overlap_utc": ["HH:MM", "HH:MM"], "overlap_minutes": N, "local_windows": [...]}; when no shared window exists it returns {"overlap": null, "verdict": "..."}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "times must be HH:MM"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| work_end | No | Working day end, 24h HH:MM; must be later than work_start. Default "17:00". | 17:00 |
| work_start | No | Working day start, 24h HH:MM local in every zone. Default "09:00". | 09:00 |
| offsets_utc | Yes | One UTC offset per participant, each between -14 and +14; fractional offsets allowed, e.g. [-8, 1, 5.5]. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
recurrence_expandRecurrence ExpandExpand a recurrence rule into a concrete list of ISO dates. FREE.
Set every_days for a fixed interval, or weekly_on for specific weekdays. Typical input {"start_date": "2026-01-05", "every_days": 14, "count": 3} returns {"dates": ["2026-01-05", "2026-01-19", "2026-02-02"]}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "start_date must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | How many dates to generate; values outside 1-60 are clamped into that range. Default 10. | |
| weekly_on | No | Weekday names to recur on, e.g. ["mon", "thu"]; full names like "monday" also work. | |
| every_days | No | Interval in days between occurrences; use this OR weekly_on, not both. | |
| start_date | Yes | First date of the series, ISO YYYY-MM-DD. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sla_dueSla DueCompute when a ticket's SLA falls due, wall-clock or business-hours. PREMIUM (license).
Typical input {"opened_at": "2026-03-02T15:30", "sla_hours": 8, "business_hours_only": true} returns {"due": "2026-03-03T15:30", "mode": "business hours 09:00-17:00"}; with business_hours_only false the mode is "wall-clock". Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "opened_at must be ISO YYYY-MM-DDTHH:MM"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| day_end | No | Business day end, 24h HH:MM; must be later than day_start. Default "17:00". | 17:00 |
| holidays | No | Optional list of ISO YYYY-MM-DD dates that never count as working days. | |
| day_start | No | Business day start, 24h HH:MM. Default "09:00". | 09:00 |
| opened_at | Yes | When the SLA clock started, ISO datetime YYYY-MM-DDTHH:MM. | |
| sla_hours | Yes | SLA length in hours; greater than 0, at most 24000; fractions allowed, e.g. 7.5. | |
| business_hours_only | No | If true, only time inside day_start-day_end on business days counts toward the SLA. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
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.
No comments yet. Be the first to start the discussion!
