Skip to main content
Glama
ampcome-mcps

Time MCP Server

by ampcome-mcps

current_time

Retrieve the current date and time in customizable formats and timezones to enable time-aware applications and accurate timestamping.

Instructions

Get the current date and time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatYesThe format of the time, default is empty stringYYYY-MM-DD HH:mm:ss
timezoneNoThe timezone of the time, IANA timezone name, e.g. Asia/Shanghai

Implementation Reference

  • The core handler function that computes the current time in UTC and the specified (or guessed) local timezone, formatting it according to the provided format string using dayjs.
    function getCurrentTime(format: string, timezone?: string) {
      const utcTime = dayjs.utc();
      const localTimezone = timezone ?? dayjs.tz.guess();
      const localTime = dayjs().tz(localTimezone);
      return {
        utc: utcTime.format(format),
        local: localTime.format(format),
        timezone: localTimezone,
      };
    }
  • Defines the Tool metadata including name, description, and input schema for the 'current_time' tool, specifying parameters for format (with enum) and optional timezone.
    export const CURRENT_TIME: Tool = {
      name: 'current_time',
      description: 'Get the current date and time.',
      inputSchema: {
        type: 'object',
        properties: {
          format: {
            type: 'string',
            description: 'The format of the time, default is empty string',
            enum: [
              'h:mm A',
              'h:mm:ss A',
              'YYYY-MM-DD HH:mm:ss',
              'YYYY-MM-DD',
              'YYYY-MM',
              'MM/DD/YYYY',
              'MM/DD/YY',
              'YYYY/MM/DD',
              'YYYY/MM',
            ],
            default: 'YYYY-MM-DD HH:mm:ss',
          },
          timezone: {
            type: 'string',
            description: 'The timezone of the time, IANA timezone name, e.g. Asia/Shanghai',
            default: undefined,
          },
        },
        required: ['format'],
      },
    };
  • src/index.ts:30-34 (registration)
    Registers the 'current_time' tool (imported as CURRENT_TIME) in the list of available tools returned by the MCP ListTools request handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [CURRENT_TIME, RELATIVE_TIME, DAYS_IN_MONTH, GET_TIMESTAMP, CONVERT_TIME, GET_WEEK_YEAR],
      };
    });
  • The dispatch handler in the CallToolRequestSchema that validates arguments, calls getCurrentTime, and formats the MCP response for the 'current_time' tool.
    case 'current_time': {
      if (!checkCurrentTimeArgs(args)) {
        throw new Error(`Invalid arguments for tool: [${name}]`);
      }
    
      const { format, timezone } = args;
      const result = getCurrentTime(format, timezone);
      return {
        success: true,
        content: [
          {
            type: 'text',
            text: `Current UTC time is ${result.utc}, and the time in ${result.timezone} is ${result.local}.`,
          },
        ],
      };
    }
  • Type guard helper function to validate the arguments for the 'current_time' tool, checking for required 'format' string and optional 'timezone' string.
    function checkCurrentTimeArgs(args: unknown): args is { format: string, timezone?: string } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'format' in args &&
        typeof args.format === 'string' &&
        ('timezone' in args ? typeof args.timezone === 'string' : true)
      );
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get the current date and time,' which implies a read-only operation, but doesn't mention any behavioral traits such as whether it requires authentication, has rate limits, or how it handles errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Get the current date and time.') that is front-loaded and wastes no words. It directly conveys the core purpose without unnecessary elaboration, making it highly concise and well-structured.

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 (simple time retrieval) and high schema coverage (100%), the description is minimally adequate. However, with no annotations and no output schema, it doesn't fully compensate for the lack of behavioral context or return value information, leaving gaps that could hinder an agent's understanding of the tool's full behavior.

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 description adds no parameter semantics beyond what the input schema provides. However, schema description coverage is 100%, with clear documentation for both parameters (format and timezone), including a default value and enum for format. This meets the baseline of 3, as the schema adequately covers parameter details without needing additional explanation in the description.

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 'Get the current date and time' clearly states the verb ('Get') and resource ('current date and time'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_timestamp' or 'relative_time', which might offer similar time-related functionality, so it doesn't reach the highest 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 'convert_time' or 'get_timestamp'. It lacks any context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone.

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