Skip to main content
Glama
SecretiveShell

MCP-timeserver

MCP-timeserver

A simple MCP server that exposes datetime information to agentic systems and chat REPLs

Components

Resources

The server implements a simple datetime:// URI scheme for accessing the current date/time in a given timezone, for example:

datetime://Africa/Freetown/now
datetime://Europe/London/now
datetime://America/New_York/now

Tools

The server exposes a tool to get the current local time in the system timezone:

>>> get_current_time()
"The current time is 2024-12-18 19:59:36"

Related MCP server: Timezone MCP Server

Quickstart

Install

use the following json

{
  "mcpServers": {
    "MCP-timeserver": {
      "command": "uvx",
      "args": ["MCP-timeserver"]
    }
  }
}

Available Tools

1 tool
get-current-timeA

Get the current time in the configured local timezone

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden of disclosure. It adds the key behavioral detail that time is in the configured local timezone, not UTC or system time. No side effects exist for a read-only clock, so this is adequate.

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?

The description is a single, front-loaded sentence with zero wasted words. Every word earns its place, conveying both action and timezone context efficiently.

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?

For a trivial stateless tool with no parameters and no output schema, the description is complete: it states what is retrieved and the timezone context. Nothing more is needed.

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?

The tool has zero parameters, and schema_description_coverage is 100% (empty schema). The baseline for 0 params is 4, and the description adds no unnecessary parameter details, so this score is appropriate.

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 uses a clear verb ('Get') and specific resource ('current time') with a relevant qualifier ('in the configured local timezone'). It unambiguously describes the tool's function, even without sibling differentiation needed.

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?

There are no sibling tools or alternatives, so explicit when-to-use guidance is unnecessary. The description provides clear context (retrieves current time), which is sufficient for this simple tool. Lacks explicit exclusions but none are needed.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedget-current-time

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clear, so an agent cannot misselect between non-existent alternatives.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (get-current-time), and with no other tools to compare, there is no inconsistency. The naming is straightforward and predictable.

Tool Count2/5

A single tool for a time server feels thin and under-scoped, as it only provides current time retrieval without obvious related operations like time conversion, formatting, or scheduling. This minimal set may limit functionality for typical time-related tasks.

Completeness2/5

The tool surface is severely incomplete for a time server domain, lacking basic operations such as converting between timezones, formatting times, or handling dates. It covers only a narrow slice of potential time-related functionality, likely causing agent failures in broader scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    Provides time and timezone functionality for LLMs, enabling them to get current time information across different timezones and convert times between zones.
    2
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables LLMs to get current time information for any timezone worldwide, including available regions, cities, and ISO 8601 formatted timestamps with timezone offsets.
    8
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides time zone management utilities including retrieving current time in any global time zone and converting time between different time zones with automatic daylight saving time handling.
    125 npm
    MIT
  • F
    license
    B
    quality
    D
    maintenance
    Provides current time and timezone conversion using IANA timezone names, with automatic system timezone detection.
    2
    -