Skip to main content
Glama

get_time

Retrieve current time in specified timezone and format for automation workflows, supporting ISO, Unix timestamp, or locale-based outputs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneNo
formatNoiso

Implementation Reference

  • The registerGetTime function that registers the 'get_time' tool on the MCP server using server.tool, defining its name, input schema, and handler function.
    function registerGetTime(server: McpServer): void {
      server.tool("get_time",
        {
          timezone: z.string().optional(),
          format: z.enum(["iso", "unix", "locale"]).optional().default(DEFAULTS.TIME_FORMAT)
        },
        async ({ timezone, format }) => {
          return wrapToolExecution(async () => {
            const info = formatTime(new Date(), format as TimeFormat, timezone);
    
            return {
              content: [{
                type: "text" as const,
                text: JSON.stringify(info, null, 2)
              }]
            };
          }, {
            errorCode: ERROR_CODES.SYSTEM_INFO,
            context: "Failed to get time"
          });
        }
      );
    }
  • Inline handler function for 'get_time' tool execution, which formats the current date and returns a standardized MCP response.
    async ({ timezone, format }) => {
      return wrapToolExecution(async () => {
        const info = formatTime(new Date(), format as TimeFormat, timezone);
    
        return {
          content: [{
            type: "text" as const,
            text: JSON.stringify(info, null, 2)
          }]
        };
      }, {
        errorCode: ERROR_CODES.SYSTEM_INFO,
        context: "Failed to get time"
      });
    }
  • Core helper function that formats the current time into the requested format (ISO, Unix timestamp, or locale) and handles timezone conversion.
    function formatTime(now: Date, format: TimeFormat, timezone?: string): TimeInfo {
      let time: string;
    
      switch (format) {
        case "unix":
          time = now.getTime().toString();
          break;
        case "locale":
          time = now.toLocaleString();
          break;
        case "iso":
        default:
          time = now.toISOString();
          break;
      }
    
      const info: TimeInfo = {
        time,
        format,
        timezone: timezone || "UTC"
      };
    
      if (timezone) {
        info.timeInTimezone = formatTimeInTimezone(now, timezone);
      }
    
      return info;
    }
  • Zod schema defining input parameters for the get_time tool: optional timezone and format.
    {
      timezone: z.string().optional(),
      format: z.enum(["iso", "unix", "locale"]).optional().default(DEFAULTS.TIME_FORMAT)
    },
  • TypeScript definitions for TimeFormat enum and TimeInfo interface used as input/output types for the get_time tool.
    export type TimeFormat = "iso" | "unix" | "locale";
    
    export interface TimeInfo {
      time: string;
      format: TimeFormat;
      timezone: string;
      timeInTimezone?: string;
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/ishuru/open-mcp'

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