Skip to main content
Glama

Time Zone Converter API - a time in many cities at once

time_zone_converter
Read-onlyIdempotent

Convert a date and time from one city to others (about 40 cities, DST-correct); empty target = main cities. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/time-zone-converter.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "New York, Tokyo",
      "from": "Sofia",
      "time": "14:30"
    },
    "name": "time_zone_converter"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCities to show, comma separated (empty = main cities)
dateNoDate YYYY-MM-DD (default today)
fromNoCity you start from, e.g. Sofia, New YorkSofia
timeNoTime 24 h, e.g. 14:3012:00

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious operational context the annotations cannot: server-side execution, files deleted after the call with nothing stored, a 25-call/day per-IP free tier, and a $0.001 paid path via x402. It stops short of describing output shape or latency.

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

Conciseness4/5

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

Three tight sentences: capability and scope first, then privacy/execution, then cost and quota. Pricing and the x402 URL are operational necessities rather than filler, though the URL makes the closing sentence slightly denser than the rest.

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

Completeness4/5

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

With four optional parameters, full schema coverage, annotations and no output schema, the main remaining questions are cost and privacy, both answered. The one gap is that the description never hints at what a response looks like (a per-city time list), which matters slightly more in the absence of an output schema.

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 description coverage is 100%, so the schema already documents all four parameters including the 'to' format and empty-target behavior. The description's only semantic addition is the '~40 cities, DST-correct' characterization of the target vocabulary, which is useful but marginal; baseline 3 applies.

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 states a specific verb and resource ('Convert a date and time from one city to others') and adds concrete scope: about 40 cities, DST-correct, empty target falls back to main cities. It is clearly not a generic date arithmetic tool like date_calculator or business_days, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied by a very legible purpose and reinforced with defaults ('from' defaults to Sofia, empty 'to' means main cities), but there is no explicit when-to-use versus a sibling such as date_calculator, and no statement of when this tool is the wrong choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources