Skip to main content
Glama
karimi-mohammad

local-time-mcp

by karimi-mohammad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_current_datetimeA

Get the current date and time.

Returns structured JSON with the current datetime, including:

  • ISO 8601 datetime string

  • Date (YYYY-MM-DD)

  • Time (HH:MM:SS)

  • Day of week in English and Persian

  • IANA timezone name

  • UTC offset

  • Unix timestamp

  • Jalali (Solar Hijri) date in numeric and Persian formats

Args: timezone: Optional IANA timezone name (e.g., "Asia/Tehran", "Europe/Berlin", "America/New_York", "UTC"). If not provided, uses system local timezone.

Returns: JSON string with datetime information, or error message for invalid timezone.

Examples: - get_current_datetime() -> Current time in system timezone - get_current_datetime("Asia/Tehran") -> Current time in Tehran - get_current_datetime("UTC") -> Current time in UTC

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

Only a single tool exists, so there is no possibility of overlap or confusion. The tool's purpose is clearly defined.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (get_current_datetime), which is consistent and descriptive.

Tool Count3/5

With only 1 tool, the server feels thin even for a focused time utility. However, the tool provides comprehensive datetime information, making the single tool non-trivial.

Completeness5/5

For its scope (returning current datetime with optional timezone), the tool fully covers the domain. It returns all relevant fields including ISO, date, time, day of week, timezone, offset, Unix timestamp, and Jalali date.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources