Skip to main content
Glama
davidan90

MCP Node Time

by davidan90

get_system_timezone

Retrieve the current system timezone to ensure accurate date and time information, addressing timezone confusion in AI responses.

Instructions

Get the system's current timezone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the 'get_system_timezone' tool by retrieving the system timezone using TimeService and augmenting with current time information in that timezone, returning structured JSON response.
    case 'get_system_timezone': {
      const systemTimezone = TimeService.getSystemTimezone();
      const currentTime = TimeService.getCurrentTime(systemTimezone, 'full');
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              systemTimezone,
              currentTime: currentTime.localizedFormat,
              utcOffset: currentTime.utcOffset,
              isDST: currentTime.isDST,
            }, null, 2),
          },
        ],
      };
    }
  • src/index.ts:72-79 (registration)
    Registers the 'get_system_timezone' tool in the tools list for ListToolsRequest, including its schema (no input params).
    {
      name: 'get_system_timezone',
      description: 'Get the system\'s current timezone',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Helper method that implements the core logic to retrieve the system's current IANA timezone identifier.
    static getSystemTimezone(): string {
      return Intl.DateTimeFormat().resolvedOptions().timeZone;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action but doesn't describe the return format (e.g., timezone name, offset), potential errors, or system dependencies. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple, parameterless tool, making it easy for an agent to parse quickly.

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 tool's simplicity (0 params, no output schema), the description is minimal but adequate for basic understanding. However, without annotations or output schema, it fails to explain what the return value includes (e.g., timezone identifier, UTC offset), which is critical for an agent to use the tool effectively in context with siblings.

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, which is correct for this case, earning a baseline score of 4 for not adding unnecessary information.

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 the resource 'system's current timezone', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_current_date' or 'get_current_time', which might provide related but distinct time information.

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 alternatives like 'get_current_time' or 'convert_time'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone.

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/davidan90/time-node-mcp'

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