Skip to main content
Glama

timeops

Server Details

Hosted MCP server for business-day math, deadline planning, meeting overlap, and SLA calculations.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
GarphenGate/moltline-mcp
GitHub Stars
0

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

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.

100% free. Your data is private.

Tool Definition Quality

Score is being calculated. Check back soon.

Available Tools

5 tools
business_daysBusiness Days
Read-onlyIdempotent
Inspect

Do 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
add_daysNoBusiness days to add; negative subtracts. Range -5000 to 5000. Ignored when end_date is provided.
end_dateNoOptional end date, ISO YYYY-MM-DD. When set, the tool counts business days between start_date and end_date instead of adding.
holidaysNoOptional list of ISO YYYY-MM-DD dates to treat as non-working days, e.g. ["2026-12-25"].
start_dateYesAnchor date in ISO format YYYY-MM-DD, e.g. "2026-03-02".

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

deadline_plannerDeadline Planner
Read-onlyIdempotent
Inspect

Plan 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
tasksYesOrdered 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_dateYesThe deadline, ISO YYYY-MM-DD.
holidaysNoOptional list of ISO YYYY-MM-DD dates treated as non-working days.
buffer_daysNoBusiness days of safety margin kept free before due_date, clamped to 0-365. Default 1.

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

meeting_overlapMeeting Overlap
Read-onlyIdempotent
Inspect

Find 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
work_endNoWorking day end, 24h HH:MM; must be later than work_start. Default "17:00".17:00
work_startNoWorking day start, 24h HH:MM local in every zone. Default "09:00".09:00
offsets_utcYesOne UTC offset per participant, each between -14 and +14; fractional offsets allowed, e.g. [-8, 1, 5.5].

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

recurrence_expandRecurrence Expand
Read-onlyIdempotent
Inspect

Expand 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
countNoHow many dates to generate; values outside 1-60 are clamped into that range. Default 10.
weekly_onNoWeekday names to recur on, e.g. ["mon", "thu"]; full names like "monday" also work.
every_daysNoInterval in days between occurrences; use this OR weekly_on, not both.
start_dateYesFirst date of the series, ISO YYYY-MM-DD.

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

sla_dueSla Due
Read-onlyIdempotent
Inspect

Compute 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
day_endNoBusiness day end, 24h HH:MM; must be later than day_start. Default "17:00".17:00
holidaysNoOptional list of ISO YYYY-MM-DD dates that never count as working days.
day_startNoBusiness day start, 24h HH:MM. Default "09:00".09:00
opened_atYesWhen the SLA clock started, ISO datetime YYYY-MM-DDTHH:MM.
sla_hoursYesSLA length in hours; greater than 0, at most 24000; fractions allowed, e.g. 7.5.
business_hours_onlyNoIf true, only time inside day_start-day_end on business days counts toward the SLA.

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    MCP server for business-day arithmetic with country-aware holiday calendars. It offers tools to check, calculate, and list business days and holidays for over 60 countries.
    9
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    An MCP server that provides deterministic, high-precision business, finance, and operational calculations such as SaaS metrics, currency conversion, business days, and financial formulas, returning structured JSON results.
    11
    MIT

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.