Skip to main content
Glama

temporal-mcp

by io.github.MirrorEthic

temporal_tick

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tz_nameNoDisplay name for the timezone (e.g. 'MDT'). Cosmetic; appears in the rendered header.
client_idNoNamespace tag (e.g. 'caweb', 'cursor'). Defaults to 'mcp'.
thread_keyNoStable 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_minutesNoCaller'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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

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.

All temporal-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
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.

Resources