Skip to main content
Glama

tick-mcp

by io.github.Cocabadger

now

Get the REAL current date and time. Call this at the start of a reply and before using any relative time words (yesterday, tomorrow, tonight, next week). Never guess time from context. NEVER write a clock time in your reply that did not come from this tool's output in THIS turn — a timestamp without a fresh call is a hallucination, even if it plausibly continues from an earlier one. ALWAYS pass the user's IANA timezone — this server is remote, so without it you get UTC, not the user's local time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneNoThe user's IANA timezone, e.g. Europe/Warsaw. Omitting it returns UTC.

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so description carries full burden. It discloses server remoteness, default UTC behavior without timezone, and emphasizes freshness to avoid hallucinations. Fully transparent about tool behavior and constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence is purposeful, but description is longer than necessary to convey the key points. However, it is well-structured with clear imperatives and front-loaded action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only one parameter and no output schema, description covers all necessary aspects: purpose, usage context, parameter importance, and common errors. Fully complete for an AI agent to use correctly.

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% but description adds value beyond schema by explaining why timezone is ALWAYS needed and consequences of omission. This provides crucial context for correct usage.

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 explicitly states 'Get the REAL current date and time' and distinguishes from sibling tool 'since' by focusing on current time versus relative time. It is specific and clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use (start of reply, before relative time words) and when-not-to-use (never guess time, never reuse timestamps). Instructs to always pass IANA timezone, making it highly actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All tick-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.7/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: 'now' returns the current date and time, while 'since' calculates relative time from a given timestamp. There is no overlap or ambiguity.

Naming Consistency5/5

Both tool names are single words in lowercase, following a simple, consistent naming style. No mixed conventions or irregularities.

Tool Count5/5

With only 2 tools, the server is tightly scoped to basic date/time utilities. This is appropriate for its purpose, as additional tools would be unnecessary for the core functionality.

Completeness4/5

The tool set covers the essential operations for a time utility: getting current time and computing relative time. A minor gap might be lack of timezone conversion or formatting, but it is largely complete for common use cases.

Resources