API Hub MCP — 337+ Tools

convert_timezone

Convert timestamps between timezones. Specify source timezone, target timezone, and optional timestamp to get the equivalent time in another zone.

Instructions

Convert timestamps between timezones.

Use this when you need to express times in a different timezone.
Supports common zones: UTC, EST, PST, CET, IST, JST, AEST, etc.

Parameters:
    timestamp — ISO date string (default: current time).
    from_tz   — Source timezone code (default: 'UTC').
    to_tz     — Target timezone code (default: 'UTC').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "convert_timezone"
  }
}

Input Schema

Name	Required	Default
`timestamp`	No
`from_tz`	No	UTC
`to_tz`	No	UTC

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.1Jun 22, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only status, destructive actions, authentication needs, error handling, or validation of timezone codes. The user is left unaware of potential failures or side effects.

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?

The description is extremely concise, using a short introductory sentence followed by a clear parameter list. Every sentence is valuable, no fluff, and the main purpose is 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?

The description covers the primary purpose and parameters but omits edge cases, error behavior, and supported timezone formats beyond a short list. Given the output schema exists, return values are likely documented, but completeness for a simple conversion tool is adequate.

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?

Despite 0% schema description coverage, the description adds meaningful parameter semantics: it explains the timestamp parameter defaults to current time, and both from_tz and to_tz default to 'UTC'. This compensates well for the schema's lack of detail.

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 clearly states the tool converts timestamps between timezones, with a specific verb and resource. However, it does not explicitly distinguish from sibling tools like time_convert or convert_timestamp, which may have overlapping functionality.

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?

The description says 'Use this when you need to express times in a different timezone,' providing clear usage context. However, it does not mention when NOT to use it or list alternative tools, limiting guidance for decision-making.

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

Deploy Server