Skip to main content
Glama
JackXuyi

Current operating environment

getTimezone

Retrieve the current device's timezone information to handle time-sensitive operations and ensure accurate scheduling across different regions.

Instructions

获取当前设备的时区信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'getTimezone' tool. Retrieves the current timezone using JavaScript's Intl.DateTimeFormat API and returns it as a JSON-formatted text response.
    case "getTimezone": {
      const timezone = Intl.DateTimeFormat().resolvedOptions().timeZone;
      return {
        content: [{
          type: "text",
          text: JSON.stringify({ timezone }, null, 2)
        }]
      };
    }
  • src/index.ts:172-180 (registration)
    Tool registration in the listTools handler. Defines the tool name, description, and input schema (empty object, no parameters required).
    {
      name: "getTimezone",
      description: "获取当前设备的时区信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema for the getTimezone tool, which requires no parameters (empty object).
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
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 what the tool does ('获取当前设备的时区信息') but doesn't describe traits like whether it's read-only (implied by 'get'), if it requires permissions, how it handles errors, or the format of returned data. 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 in Chinese ('获取当前设备的时区信息'), which directly states the purpose without any waste. It's front-loaded with the core action and resource, making it highly concise and well-structured for quick understanding.

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 (0 parameters, no output schema, no annotations), the description is minimally complete—it tells what the tool does. However, it lacks details on behavioral aspects (e.g., data format, error handling) and usage context, which are gaps even for a simple tool. It meets the basic requirement but doesn't provide rich contextual information.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics beyond the schema, but this is appropriate given the lack of parameters. A baseline of 4 is assigned as it adequately handles the parameter-free case without unnecessary details.

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 ('获取' meaning 'get') and resource ('时区信息' meaning 'timezone information'), specifying it retrieves timezone data for the current device. It distinguishes from siblings by focusing on timezone rather than other system metrics like battery, network, or hardware info. However, it doesn't explicitly contrast with a hypothetical alternative like 'setTimezone', which slightly limits differentiation.

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. It doesn't mention prerequisites (e.g., device access), exclusions (e.g., not for historical timezone data), or compare to sibling tools like getPlatformInfo (which might include timezone). Usage is implied only by the tool name and description, lacking explicit context.

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/JackXuyi/env-mcp'

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