Skip to main content
Glama
odgrim

MCP DateTime

by odgrim

get-current-timezone

Retrieve the current system timezone to enable accurate datetime handling for AI agents and chat interfaces.

Instructions

Get the current system timezone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:31-43 (registration)
    Registers the 'get-current-timezone' tool with the MCP server, including inline handler function that retrieves and returns the current system timezone.
    server.tool(
      "get-current-timezone",
      "Get the current system timezone",
      async () => {
        const timezone = getCurrentTimezone();
        return {
          content: [{ 
            type: "text", 
            text: `The current system timezone is ${timezone}`
          }]
        };
      }
    );
  • Inline handler function for the tool that calls getCurrentTimezone() and formats the response as text content.
    async () => {
      const timezone = getCurrentTimezone();
      return {
        content: [{ 
          type: "text", 
          text: `The current system timezone is ${timezone}`
        }]
      };
    }
  • Core helper function that implements the logic to get the current system timezone using Intl.DateTimeFormat().resolvedOptions().timeZone, with fallback to UTC.
    export function getCurrentTimezone(): string {
      try {
        const timezone = Intl.DateTimeFormat().resolvedOptions().timeZone;
        return processTimezone(timezone);
      } catch (error) {
        console.error("Error getting current timezone:", error);
        return "UTC"; // Default to UTC if there's an error
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose whether this is a read-only operation, if it requires permissions, how it handles errors, or what format the timezone is returned in (e.g., IANA code, offset).

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, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently conveys the essential information without unnecessary elaboration.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool that returns data. It doesn't specify what the output looks like (e.g., timezone name, offset, or structured object), which is critical for an agent to use the tool effectively. The simplicity of the tool mitigates this somewhat, but key behavioral context is missing.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't mention parameters, aligning with the schema. A baseline of 4 is applied since no parameters exist.

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 action ('Get') and resource ('current system timezone'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-current-time' or 'list-timezones', which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives like 'get-current-time' (which might return time without timezone) or 'list-timezones' (which lists available timezones). The description lacks context about use cases or exclusions.

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

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/odgrim/mcp-datetime'

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