Taghvim
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nowA | Return the current deterministic time. Do NOT let the LLM infer the current date/time — call this tool instead. Returns UTC and local time, weekday, UTC offset, and DST status. |
| resolve_timeA | Resolve a natural-language date/time expression into a deterministic ISO timestamp. Use this whenever the user mentions relative dates ('tomorrow', 'next Friday', 'in two weeks', 'the first Monday of next month'). The LLM interprets the language; this tool performs the actual temporal computation. Returns structured result with UTC, local, and precision info. |
| calculate_dateA | Perform deterministic date arithmetic: add/subtract units, snap to day/week/month/quarter/year boundaries, or compute differences between dates. Handles leap years and month-end edge cases correctly. Example: 2026-01-31 + 1 month → 2026-02-28. |
| convert_timeA | Convert a datetime between IANA timezones. Correctly handles DST transitions and date-boundary changes. Never hardcodes UTC offsets. Use IANA timezone names (e.g. 'America/New_York', 'Asia/Tokyo'). Can convert to multiple timezones at once. |
| timezone_infoA | Get deterministic timezone information: UTC offset, DST status, abbreviation, and next/previous DST transitions. Uses the IANA timezone database. Handles zones with no DST correctly. |
| business_daysA | Business-day calculations: check if a date is a business day, find next/previous business day, add business days, count business days between dates. Supports configurable weekends and public holidays by country (US, UK, DE, JP, IR, UAE, etc.). Does NOT assume Saturday/Sunday weekend globally. |
| holidaysA | Public holiday intelligence: list all holidays for a country and year, check if a specific date is a holiday, find the next upcoming holiday, or get holidays in a date range. Supports 100+ countries via the IATA holiday database. Distinguishes between actual and observed holiday dates. |
| recurrenceA | Generate recurring date schedules using RFC 5545 RRULE. Supports natural language patterns ('every Monday', 'first Friday of every month', 'every 90 days') converted deterministically to RRULE where possible. Always generates bounded results within a date range. Never generates infinite recurrences. |
| calendarC | Calendar system operations: convert between Gregorian, Persian/Jalali, and ISO week calendars. Validate dates, get weekday information, generate month calendars. Persian/Jalali is a first-class supported calendar. |
| format_timeB | Deterministically format a datetime string. Supports ISO 8601, RFC 3339, locale-aware formats (en-US, de-DE, ja-JP, fa-IR, etc.), Jalali, human-readable, and custom Luxon format strings. Use Intl.DateTimeFormat for locale-specific output. |
| temporal_verifyA | Verify a temporal claim deterministically. Prevents temporal hallucinations by checking facts like: 'Is 2026-12-31 a Thursday?', 'Is December 25 2027 a Saturday?', 'Is 3 PM London before 10 AM New York?', 'Is 2024 a leap year?'. Always returns structured facts. |
| jalali_persianA | Persian/Jalali calendar operations: convert dates, look up events, get month overviews, calculate days until Jalali dates. This is a convenience wrapper for Jalali-specific functionality. For universal calendar operations, use the 'calendar' tool instead. |
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/mrfelfel/taghvim'
If you have feedback or need assistance with the MCP directory API, please join our Discord server