Skip to main content
Glama
batteryshark

DateTime MCP Server

by batteryshark
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

DateTime MCP Server

A simple MCP server that provides timezone-aware date and time information.

Tools

  • get_current_date(include_weekday=False) - Returns current date in ISO format (YYYY-MM-DD) with optional weekday

  • get_current_time() - Returns current time in configured format

Related MCP server: Date and Time MCP Server

Configuration

Set these environment variables (for stdio) or headers (for HTTP):

  • DEFAULT_TZ - Timezone identifier (e.g., "America/New_York", "Europe/London", "UTC")

  • TIMEFMT - Time format: "12" for 12-hour (2:30 PM) or "24" for 24-hour (14:30)

Fallbacks

  • Invalid timezone → defaults to UTC

  • TIMEFMT not "12" → defaults to 24-hour format

Usage Examples

STDIO (default)

{
  "date-time-mcp": {
    "command": "uv",
    "args": ["run", "python", "server.py"],
    "env": {
      "DEFAULT_TZ": "America/New_York",
      "TIMEFMT": "12"
    }
  }
}

HTTP Server

{
  "date-time-mcp": {
    "url": "http://localhost:8855",
    "headers": {
      "DEFAULT_TZ": "America/New_York",
      "TIMEFMT": "24"
    }
  }
}

Available Tools

2 tools
get_current_dateA

Get the current date in ISO format (YYYY-MM-DD).

Args: include_weekday: Whether to append the day of the week

Returns: ISO date string, optionally with weekday

Examples: get_current_date() -> "2024-01-15" get_current_date(include_weekday=True) -> "2024-01-15 (Monday)"

ParametersJSON Schema
NameRequiredDescriptionDefault
include_weekdayNo

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it returns the current date in a specific format, optionally with the weekday appended. However, it lacks details on potential limitations like timezone handling or system dependencies.

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 well-structured with clear sections (description, args, returns, examples), front-loaded key information, and no redundant sentences. Each part adds value, making it efficient and easy to parse.

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 tool's low complexity (1 parameter, no output schema, no annotations), the description is nearly complete. It covers purpose, parameters, and return values with examples. A minor gap is the lack of explicit error handling or timezone context, but overall it provides sufficient information for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must fully compensate. It clearly explains the single parameter 'include_weekday' and its effect on the output, including examples that illustrate the semantics beyond the schema's boolean type.

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 the tool's purpose with a specific verb ('Get') and resource ('current date'), including the output format ('ISO format (YYYY-MM-DD)'). It clearly distinguishes from the sibling tool 'get_current_time' by focusing on date rather than time.

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

Usage Guidelines3/5

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

The description implies usage through examples showing when to include the weekday parameter, but it does not explicitly state when to use this tool versus alternatives like 'get_current_time' or other date-related tools. No guidance on exclusions or prerequisites is provided.

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

get_current_timeA

Get the current time in the configured format.

Returns: Time string in 12-hour or 24-hour format based on TIMEFMT setting

Examples: With TIMEFMT="12": "2:30 PM" With TIMEFMT="24": "14:30"

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the output format depends on a TIMEFMT setting, which is useful behavioral context. However, it does not mention other traits like whether this is a read-only operation, potential errors, or performance considerations.

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 well-structured and concise, with a clear purpose statement followed by returns and examples sections. Every sentence adds value without waste, and it is front-loaded with the core functionality.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains what the tool does, the output format dependency, and provides examples. However, it could be more explicit about sibling tool differentiation.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on output behavior without redundant parameter info, earning a baseline score of 4 for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get the current time in the configured format.' It specifies the verb ('Get') and resource ('current time'), but does not explicitly differentiate from its sibling tool 'get_current_date'. The distinction is implied but not stated.

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

Usage Guidelines3/5

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

The description implies usage context through the mention of 'configured format' and TIMEFMT setting, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'get_current_date'). No exclusions or prerequisites are mentioned.

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. Dates show when Glama detected each change.

  1. 2 tool updates
    • First observedget_current_date
    • First observedget_current_time
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: get_current_date retrieves date information, while get_current_time retrieves time information. There is no overlap in functionality, and an agent would easily differentiate between them based on their names and descriptions.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'get_current_' prefix, using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

Tool Count2/5

With only two tools, the server feels thin for a DateTime domain. A comprehensive DateTime server would typically include tools for date/time manipulation, formatting, timezone handling, or date arithmetic, not just current date and time retrieval.

Completeness2/5

The toolset is severely incomplete for a DateTime server. It lacks basic operations like date/time parsing, formatting control, timezone conversions, date arithmetic (add/subtract days), or comparisons. Agents will hit dead ends when needing anything beyond current date/time retrieval.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Time Server

    clssck
    F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server providing timezone conversions and time-related operations via RESTful API endpoints, featuring comprehensive error handling and timezone database integration.
    -

  • DateTime MCP Server

    TakanariShimbo
    A
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol server that provides tools to get the current date and time in various formats, supporting different timezones and custom formatting options.
    1
    29
    1
    MIT

  • Time & Location MCP Server

    SergeSerb2
    F
    license
    B
    quality
    D
    maintenance
    An MCP server that automatically detects and provides current time and location information based on system timezone and IP geolocation.
    2
    -

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/batteryshark/mcp-datetime'

If you have feedback or need assistance with the MCP directory API, please join our Discord server