Skip to main content
Glama
t-shiratori

Time Tools MCP Server

get_timezone

Retrieve timezone information like Asia/Tokyo for accurate time calculations and scheduling across different regions.

Instructions

Get timezone (e.g. Asia/Tokyo)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler and registration for the get_timezone tool. It calls the getTZ helper to return the current timezone as text content.
    server.tool("get_timezone", "Get timezone (e.g. Asia/Tokyo)", async () => {
        return {
            content: [
                {
                    type: "text",
                    text: getTZ(),
                },
            ],
        };
    });
  • Helper function getTZ used by get_timezone (and other tools) to determine the timezone, defaulting to dayjs.tz.guess() if not provided.
    const getTZ = (timezon?: string) => {
        return timezon || dayjs.tz.guess();
    };
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. The description only states what the tool returns ('timezone') without explaining how it determines which timezone, whether it requires any context or permissions, what format the return value uses, or whether it's static or dynamic. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 (5 words plus an example) and front-loaded with the core purpose. Every word earns its place - 'Get' specifies the action, 'timezone' specifies the resource, and the example provides helpful clarification. No wasted words or unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what kind of timezone is returned (system default? user preference? based on location?), the return format, or any behavioral characteristics. For a tool that might have implementation nuances (e.g., server timezone vs. client timezone), more context is needed despite the simple parameterless design.

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 zero parameters, and schema description coverage is 100% (though the schema is empty). The description appropriately doesn't discuss parameters since none exist. It focuses on the return value ('timezone') which is correct for a parameterless tool. Baseline for zero parameters is 4.

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 ('timezone'), and provides a helpful example ('Asia/Tokyo'). It distinguishes from siblings by focusing on timezone retrieval rather than datetime conversion or elapsed time calculations. However, it doesn't explicitly differentiate from all siblings (like get_current_date_time which might also return timezone).

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. With multiple sibling tools for datetime operations (convert_datetime_to_unix, get_current_date_time, etc.), there's no indication whether this returns the system timezone, a user's timezone, or supports location-based lookup. No explicit when/when-not or alternative recommendations are provided.

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