Skip to main content
Glama

getCurrentTime

Retrieve and format the current time for any locale or time zone using Intl.DateTimeFormat.

Instructions

Get current time formatted with Intl.DateTimeFormat

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoLocale for formatting (e.g., en-US)en-US
timeZoneNoTime zone (e.g., America/New_York)UTC

Implementation Reference

  • The async handler function for the getCurrentTime tool. It formats the current time using Intl.DateTimeFormat with provided locale and timeZone parameters.
    handler: async ({ locale = 'en-US', timeZone = 'UTC' }) => {
      const formatter = new Intl.DateTimeFormat(locale, {
        timeZone,
        year: 'numeric',
        month: 'numeric',
        day: 'numeric',
        hour: 'numeric',
        minute: 'numeric',
        second: 'numeric',
        timeZoneName: 'short'
      });
      
      return {
        content: [{
          type: 'text',
          text: formatter.format(Date.now())
        }]
      };
    }
  • Input schema for the getCurrentTime tool, defining optional locale and timeZone parameters.
    inputSchema: {
      type: 'object',
      properties: {
        locale: {
          type: 'string',
          description: 'Locale for formatting (e.g., en-US)',
          default: 'en-US'
        },
        timeZone: {
          type: 'string',
          description: 'Time zone (e.g., America/New_York)',
          default: 'UTC'
        }
      }
    },
  • src/index.ts:28-35 (registration)
    Registration of systemTools (containing getCurrentTime) into the allTools object used by the MCP server for tool listing and execution.
    const allTools: ToolKit = {
      ...systemTools,
      ...networkTools,
      ...geoTools,
      ...generatorTools,
      ...dateTimeTools,
      ...securityTools
    };
  • src/index.ts:5-5 (registration)
    Import of systemTools which includes the getCurrentTime tool definition.
    import { systemTools } from './tools/system.js';
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 formatting but doesn't specify whether this is a read-only operation, if it requires system permissions, what happens on errors, or the exact format of the returned time. This leaves significant gaps for a tool that interacts with system time.

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 uses precise technical terminology (Intl.DateTimeFormat) without unnecessary elaboration.

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

Completeness3/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 (no output schema, no annotations, simple parameters), the description is minimally adequate. However, it lacks details about return values or error handling, which would be helpful even for a simple tool. It's complete enough to understand the basic function but not robustly informative.

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 input schema has 100% description coverage, clearly documenting both parameters (locale and timeZone) with defaults. The description adds no additional parameter details beyond what the schema provides, 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 tool's purpose with a specific verb ('Get') and resource ('current time'), and specifies formatting via Intl.DateTimeFormat. However, it doesn't explicitly distinguish this from sibling tools like convertTimezone or listTimezones, 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?

The description provides no guidance on when to use this tool versus alternatives like convertTimezone or listTimezones, nor does it mention any prerequisites or exclusions. It only states what the tool does, not when it's appropriate.

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/cyanheads/toolkit-mcp-server'

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