Vreme Temporal MCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_timeA | Query temporal information using natural language. Get current time, timezone info, 9 cultural calendars (Hebrew, Islamic, Chinese, Hindu, Persian, Buddhist, Bahá'í, Ethiopian, Mayan), astronomical events, religious fasting status, work restrictions, and activity appropriateness for any location. Supports queries like 'What time is it in Tokyo?', 'Is it a good time to call Berlin?', 'Is it Shabbat in Jerusalem?', 'When is sunrise in Paris?', 'Is it Ramadan?', etc. |
| query_prayer_timesA | Get Islamic prayer times (Salah/Namaz) for any location. Returns all 5 daily prayers (Fajr, Dhuhr, Asr, Maghrib, Isha), next prayer time, and Qibla direction to Mecca. Calculation method is automatically selected based on location (MWL, ISNA, Egypt, Makkah, Karachi, Tehran, Jafari). Supports queries for specific prayers or all prayers. |
| check_activity_appropriatenessA | Check if the current time is appropriate for specific activities (calls, work, meetings) in a given location. Takes into account time of day, cultural/religious observances across 9 calendar systems (Shabbat, Ramadan fasting, religious holidays from Hebrew, Islamic, Hindu, Buddhist, and other traditions), work restrictions, and local customs. Perfect for 'Can I call someone in X?' or 'Is it a good time to contact Y?' queries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The tools have significant overlap, particularly between 'check_activity_appropriateness' and 'query_time', as both handle activity appropriateness, cultural/religious observances, and work restrictions. 'query_prayer_times' is more distinct but still overlaps with the Islamic calendar aspects of the other tools, leading to potential confusion for an agent trying to select the right tool.
All tool names follow a consistent verb_noun pattern with snake_case, using clear verbs like 'check', 'query', and 'query' again. The naming is predictable and readable, with no deviations in style or convention across the three tools.
With only 3 tools, the server feels thin for its broad scope covering temporal information, cultural calendars, religious observances, and activity appropriateness. This limited set may not fully support complex workflows, as agents might need more specialized tools for distinct aspects like calendar conversions or event tracking.
The tool surface has significant gaps for the inferred domain of temporal and cultural information. For example, there are no tools for creating or updating calendar events, converting between different calendar systems, or managing user-specific preferences. The existing tools provide querying capabilities but lack lifecycle operations, making the server incomplete for comprehensive temporal management tasks.