Agent Tools

timezone_convert

Convert time between timezones for scheduling meetings and coordinating deadlines across IANA time zones. DST-correct UTC offsets. time=ISO local time or 'now'. Price $0.001 USDC per call via x402. Example output: {"utc":"2026-10-22T16:00:00.000Z","from":{"timezone":"America/New_York","local":"2026-10-22T12:00:00","utc_offset":"-04:00"},"to":{"timezone":"Asia/Tokyo","local":"2026-10-23T01:00:00","utc_offset":"+09:00"}}

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

Input Schema

Name	Required	Description
`to`	Yes	IANA zone, e.g. Asia/Tokyo
`from`	Yes	IANA zone, e.g. America/New_York
`time`	No	ISO local time or 'now'

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses DST correctness, a per-call price of $0.001 USDC via x402 (a real cost/auth-relevant fact), and a concrete output example. It stops short of stating error behavior for invalid IANA zones or what happens when the optional time parameter is omitted.

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?

Front-loaded with purpose, then behavior, then price, then example — a sensible ordering with little wasted wording. The embedded JSON example is long but earns its space because there is no output schema.

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?

For a 3-parameter conversion utility with no output schema and no annotations, the description covers purpose, DST handling, cost, and return shape via example. Remaining gaps are edge-case behavior (invalid zone, omitted time) rather than anything blocking a correct call.

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 from/to/time are already documented, which sets the baseline at 3. The example output implicitly shows that the supplied local time is interpreted in the 'from' zone, but the description never states this explicitly, so it adds only indirect value.

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 and resource ('Convert time between timezones') and pins the domain to IANA time zones with DST-correct offsets. An agent can immediately tell this apart from scheduling-adjacent siblings like business_day_add or fx_convert.

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?

Provides positive use cases ('scheduling meetings', 'coordinating deadlines') but gives no when-not conditions, no prerequisites, and does not name an alternative tool for adjacent needs such as business-day arithmetic. Usage is implied by scenario rather than stated as a selection rule.

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

All Agent 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?