Tanod MCP server

utilpeek: convert a time between IANA time zones

convert_time

Read-onlyIdempotent

Convert a timestamp or current instant across up to 20 IANA time zones; specify the source zone for offset-free times and detect DST gaps or ambiguities.

Instructions

utilpeek: convert one instant between time zones. For business days use count_or_add_business_days. Zones come from the pinned IANA tz database (tzdata package), not the host; a wall time in a DST gap or fold is flagged nonexistent / ambiguous; a time with an offset plus from_tz is a 422. An unknown zone or a malformed time is a 422 (not charged). Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/timezone-converter-api.html

Input Schema

TableJSON Schema

Name	Required	Description
`time`	No	Optional ISO 8601 date-time or Unix seconds (default now).
`to_tz`	Yes	1-20 IANA time zones to convert to.
`from_tz`	No	Optional IANA zone of a time WITHOUT an offset (default UTC).

Output Schema

TableJSON Schema

Name	Required	Description
`utc`	No
`unix`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`input`	No
`source`	No
`conversions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description goes further with tzdata source, DST gap/fold flags, 422 error semantics, 'not charged' for invalid input, latency, price, and daily free tier—rich context beyond structured fields.

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?

Front-loads the core conversion purpose, then the alternative, then behavioral details. Dense but every clause carries actionable information (errors, latency, pricing, docs).

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

Completeness5/5

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

An output schema exists, so return format needn't be described. Given 3 parameters, 100% schema coverage, and annotations, the description supplies all missing operational context an agent needs.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics: from_tz cannot be combined with an offset-bearing time, and DST gap/fold times are flagged, which are not in the schema descriptions.

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') and resource ('one instant between time zones'), and names the sibling to use for business-day math. An agent can distinguish it from count_or_add_business_days without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes business-day needs to count_or_add_business_days and describes error conditions (offset plus from_tz, unknown zone, malformed time) that define when this tool will not work. No other time-conversion alternative is needed from the sibling list.

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

Deploy Server