Skip to main content
Glama
ssinha3

Time MCP Server

by ssinha3

get_current_time

Retrieve the current time and date for a specified IANA timezone using the Time MCP Server. Input the timezone name to get accurate local time information for global applications.

Instructions

Get current time in a specific timezones

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneYesIANA timezone name (e.g., 'America/New_York', 'Europe/London'). Use 'Etc/UTC' as local timezone if no timezone provided by the user.

Implementation Reference

  • The main handler function for the 'get_current_time' tool. It takes a timezone_name, retrieves the ZoneInfo object, gets the current datetime in that timezone, and returns a TimeResult object containing the timezone, ISO-formatted datetime string, and DST status.
    def get_current_time(self, timezone_name: str) -> TimeResult:
        """Get current time in specified timezone"""
        timezone = get_zoneinfo(timezone_name)
        current_time = datetime.now(timezone)
    
        return TimeResult(
            timezone=timezone_name,
            datetime=current_time.isoformat(timespec="seconds"),
            is_dst=bool(current_time.dst()),
        )
  • Pydantic model defining the structured output for the get_current_time tool response.
    class TimeResult(BaseModel):
        timezone: str
        datetime: str
        is_dst: bool
  • Tool registration in the MCP server's list_tools pipeline, defining the tool's name, description, and input schema which requires a 'timezone' parameter as a string.
    Tool(
        name=TimeTools.GET_CURRENT_TIME.value,
        description="Get current time in a specific timezones",
        inputSchema={
            "type": "object",
            "properties": {
                "timezone": {
                    "type": "string",
                    "description": f"IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Use '{local_tz}' as local timezone if no timezone provided by the user.",
                }
            },
            "required": ["timezone"],
        },
    ),
  • Utility function to create a ZoneInfo object from a timezone name string, with error handling for invalid timezones. Called by the get_current_time handler.
    def get_zoneinfo(timezone_name: str) -> ZoneInfo:
        try:
            return ZoneInfo(timezone_name)
        except Exception as e:
            raise McpError(f"Invalid timezone: {str(e)}")
  • String enum defining the canonical names for time-related tools, used in registration and dispatch.
    class TimeTools(str, Enum):
        GET_CURRENT_TIME = "get_current_time"
        CONVERT_TIME = "convert_time"
Behavior2/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 mentions getting current time but doesn't specify whether this requires authentication, has rate limits, returns errors for invalid timezones, or provides output format details. This leaves significant gaps for a tool that interacts with time data.

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, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a simple tool with one parameter and gets straight to the point.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the output looks like (e.g., timestamp format, timezone handling), error conditions, or behavioral constraints. The simplicity of the tool doesn't compensate for these missing contextual elements.

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

Parameters3/5

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

The schema description coverage is 100%, with the parameter 'timezone' fully documented in the schema (including IANA format and default behavior). The description adds no additional parameter information beyond what's in the schema, so it meets the baseline for high schema coverage.

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 verb 'Get' and resource 'current time' with the scope 'in a specific timezone', making the purpose understandable. However, it doesn't explicitly differentiate from the sibling tool 'convert_time', which likely handles time conversion rather than current time retrieval.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus the sibling 'convert_time' or any alternatives. It lacks context about when this tool is appropriate versus other time-related operations, offering only a basic functional statement.

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

Install Server

Other Tools

Related Tools

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/ssinha3/mcp-time-server'

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