Skip to main content
Glama
t-shiratori

Time Tools MCP Server

get_current_date_time_iso

Retrieve the current date and time in ISO 8601 format for standardized timestamping and timezone-aware applications.

Instructions

Get ISO 8601 time. (e.g. 2025-05-07T23:03:27+09:00)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneNo

Implementation Reference

  • The asynchronous handler function that executes the tool logic: gets current datetime in ISO 8601 format using dayjs library, applies optional timezone via getTZ helper, and returns it as text content.
    async ({ timezone }) => {
        const currentDateTime = dayjs().tz(getTZ(timezone)).format();
        return {
            content: [
                {
                    type: "text",
                    text: currentDateTime,
                },
            ],
        };
    },
  • Input schema definition using Zod: optional 'timezone' string parameter.
    {
        timezone: z.string().optional(),
    },
  • src/index.ts:112-129 (registration)
    Registration of the 'get_current_date_time_iso' tool on the MCP server, specifying name, description, input schema, and handler function.
    server.tool(
        "get_current_date_time_iso",
        "Get ISO 8601 time. (e.g. 2025-05-07T23:03:27+09:00)",
        {
            timezone: z.string().optional(),
        },
        async ({ timezone }) => {
            const currentDateTime = dayjs().tz(getTZ(timezone)).format();
            return {
                content: [
                    {
                        type: "text",
                        text: currentDateTime,
                    },
                ],
            };
        },
    );
  • Helper function to determine timezone: uses provided value or guesses via dayjs.tz.guess() if omitted.
    const getTZ = (timezon?: string) => {
        return timezon || dayjs.tz.guess();
    };
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 states the tool returns current time in ISO 8601 format with an example, but doesn't mention if it's read-only, requires permissions, has rate limits, or how it handles the optional timezone parameter. This leaves gaps in understanding the tool's behavior beyond basic output format.

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 extremely concise—a single sentence with a helpful example. It's front-loaded with the core purpose and wastes no words, making it easy for an agent to parse quickly. Every element earns its place.

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 (single optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the output format with an example, but lacks details on parameter usage, behavioral traits, or differentiation from siblings. For a simple time-fetching tool, it's passable but leaves room for improvement in context.

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 one parameter 'timezone' with 0% description coverage. The tool description doesn't mention parameters at all, failing to compensate for the schema gap. However, with only one optional parameter, the baseline is moderate, but the description adds no value beyond what the bare schema provides.

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 'ISO 8601 time', with an example format provided. It distinguishes from siblings like 'get_current_date_time' by specifying the ISO format, though it doesn't explicitly contrast with all siblings. The purpose is specific and actionable.

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_date_time' or 'get_unixtime'. The description implies usage for obtaining current time in ISO format, but lacks explicit when/when-not instructions or named alternatives, leaving the agent to infer based on format differences.

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/t-shiratori/time-tools-mcp-server'

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