A
licenseA
qualityB
maintenanceProvides accurate system time to LLM applications with multi-timezone support via a simple tool call.
1
MIT
temporal-mcp
Server Details
Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- MirrorEthic/temporal-mcp
- GitHub Stars
- 2
- Server Listing
- temporal-mcp
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
A4/5.0
Tool DescriptionsA
Average 4/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools have clearly distinct purposes: one reads the current temporal snapshot without advancing state, and the other advances the clock and returns a snapshot. No overlap or ambiguity.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern with the 'temporal_' prefix, using clear verbs ('peek' and 'tick') that accurately describe their actions.
Tool Count4/5
With only two tools, the server is minimal but fits a narrow domain of temporal state management. It is slightly on the thin side but still reasonable for the intended purpose.
Completeness4/5
The tools cover the core operations of reading and advancing temporal state. A potential gap is the absence of a reset or manual set tool, but for the described use case (per-turn gap tracking) the set is complete.
Available Tools
2 toolstemporal_peekAInspect
Read the current temporal snapshot for a thread WITHOUT advancing state. Use this when you want the gap delta but the call is not the canonical per-turn event.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tz_name | No | ||
| client_id | No | ||
| thread_key | No | ||
| tz_offset_minutes | No |
Tool Definition Quality
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses the key behavior (non-advancing state) but lacks details on side effects, permissions, or rate limits. Adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences that front-load the main purpose and usage condition, with no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers core purpose but fails to explain parameter meanings or return value, which is critical given no output schema and 4 undocumented parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 4 parameters with 0% description coverage, and the tool description provides no explanation or context for any parameter, leaving the agent to guess.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it reads a temporal snapshot without advancing state, and distinguishes from the sibling tool temporal_tick which likely advances state.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use: when wanting the gap delta but not the canonical per-turn event. This provides useful context, though could be more explicit about when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
temporal_tickAInspect
Advance the temporal clock for a thread and return a snapshot (now / prev / gap / day_rollover / fresh_thread). Call once per user turn. Pass a stable thread_key (e.g. the conversation ID) so gap deltas remain meaningful across page reloads.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tz_name | No | Display name for the timezone (e.g. 'MDT'). Cosmetic; appears in the rendered header. | |
| client_id | No | Namespace tag (e.g. 'caweb', 'cursor'). Defaults to 'mcp'. | |
| thread_key | No | Stable thread identifier within this client. For claude.ai web use the conversation ID; for other MCP clients any caller-stable string. If omitted, falls back to the Mcp-Session-Id header. | |
| tz_offset_minutes | No | Caller's UTC offset in minutes (e.g. -360 for MDT). Used for day_rollover detection and header formatting. Defaults to 0 (UTC) so day rollover is always honest even if the caller forgets to pass one. |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the tool mutates state (advances clock) and includes details like ensuring gap deltas remain meaningful. With no annotations provided, it adequately carries the transparency burden.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each essential: core action, call frequency, and parameter guidance. No fluff, information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of an output schema and annotations, the description covers the main functionality, usage constraints, and return components. It could detail the snapshot structure more, but the listed components are sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds value beyond the schema by explaining the purpose of thread_key for stable identification across reloads. Other parameters are not elaborated, but the extra context justifies a 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool advances the temporal clock for a thread and returns a snapshot with specified components (now, prev, gap, day_rollover, fresh_thread). The verb 'Advance' and the resource are specific, and the action implicitly distinguishes it from the sibling 'temporal_peek'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides clear usage context: call once per user turn and pass a stable thread_key. However, it does not explicitly compare with the sibling tool or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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!
Related MCP Servers
- AlicenseBqualityDmaintenanceGiving LLMs Time Awareness Capabilities. Empower your LLMs with time awareness capabilities. Access current time, convert between timezones, and get timestamps effortlessly. Enhance your applications with precise time-related functionalities.61,01469MIT
- MIT
- Flicense-qualityCmaintenanceProvides current time, relative time, timezone conversion, timestamps, and more for LLMs.
Try in Browser
Your Connectors
Sign in to create a connector for this server.