Crypto, web, finance and app data tools

Time Zone Converter

time_zone_convert

Convert a date-time (or now) from one time zone to several others, by IANA name, city or abbreviation (Dubai, New York, PST, CET): local time, UTC offset, abbreviation, DST flag and weekday. Use to schedule meetings across time zones.

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": {
      "to": "<to>"
    },
    "name": "time_zone_convert"
  }
}

Input Schema

Name	Required	Default
`to`	Yes
`time`	No
`from_zone`	No	UTC

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations, so the description carries the burden. It usefully discloses that 'now' is accepted and that multiple target zones are supported, plus the returned fields. However, it omits how invalid zones/formats are handled, and whether 'to' accepts multiple values is left ambiguous despite the string schema. Adequate but with clear gaps.

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?

Two dense sentences, front-loaded with the core action and input scope. The enumerated output fields are somewhat redundant given an output schema exists, but overall there is little waste.

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?

With an output schema, return values needn't be explained, and the description covers input flexibility and purpose. But for a 3-parameter tool with 0% schema coverage, missing default ('from_zone' = UTC) and format details, plus the ambiguous 'to' string vs 'several others' claim, leave material gaps an agent would need.

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 0%, so the description must compensate. It partially does: zone inputs accept IANA names, cities, or abbreviations with examples, and 'time' may be a date-time or omitted for 'now'. But it never maps these to parameter names, never states that 'from_zone' defaults to UTC, never specifies a concrete time format, and doesn't clarify whether 'to' is a single or comma-separated multi-zone string.

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?

States a specific verb (Convert), resource (date-time/time zone), and scope (one zone to several others) with concrete supported input forms. No sibling tool overlaps, and an agent can immediately tell what this does.

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

Usage Guidelines4/5

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

Provides a clear use case ('Use to schedule meetings across time zones.') but no explicit exclusions or alternatives. Reasonable given no sibling competes, but it doesn't say when not to use it or how it differs from general date tools.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?