Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_geo_timezone

Look up the IANA timezone, UTC offset, and current local time for a given city by entering a city name in Chinese or English.

Instructions

Timezone lookup by city / city timezone API / Chinese city timezone / city UTC offset / 时区查询 / IANA timezone name / city local time / DST aware timezone lookup / timezone by city name. Look up the IANA timezone, UTC offset, and current local time for a given city.

Price: unknown on Base (auto-paid in USDC).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "cn402_geo_timezone"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name in Chinese or English (required, e.g. 北京/Beijing/Tokyo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The description mentions DST-aware lookup, which adds behavioral context beyond the schema. However, no annotations are provided, and it omits error handling, rate limits, or authentication needs.

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

Conciseness3/5

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

The description includes a cluttered list of keywords and pricing info unrelated to functionality. It could be more streamlined and front-loaded.

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 single parameter and no output schema, the description is somewhat complete but lacks details on ambiguous city names, error cases, or response format.

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?

Schema coverage is 100% with a clear parameter description. The tool's description adds examples (北京/Beijing/Tokyo) but doesn't significantly enhance meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the tool looks up IANA timezone, UTC offset, and current local time for a city, using specific verbs and resource. It distinguishes from siblings like cn402_geo_cn_city which are purely geographic.

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 vs alternatives like cn402_timepoint or cn402_time_timezone-convert. It only lists keywords without context for selection.

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

Deploy Server

Other Tools