GadgetHumans API Hub

by io.github.scotia1973-bot

convert_timezone

Convert timestamps between any timezones

Input Schema

Name	Required	Description
`to_tz`	No	Target timezone e.g. EST
`from_tz`	No	Source timezone e.g. UTC
`timestamp`	No	ISO date string (default: now)

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 10, 2026

removedInput schema / properties / from_tz / default
```
Removed value: -"UTC"
```
addedInput schema / properties / from_tz / description
```
Added value: +"Source timezone e.g. UTC"
```
removedInput schema / properties / from_tz / title
```
Removed value: -"From Tz"
```
removedInput schema / properties / timestamp / default
```
Removed value: -""
```
addedInput schema / properties / timestamp / description
```
Added value: +"ISO date string (default: now)"
```
removedInput schema / properties / timestamp / title
```
Removed value: -"Timestamp"
```
removedInput schema / properties / to_tz / default
```
Removed value: -"UTC"
```
addedInput schema / properties / to_tz / description
```
Added value: +"Target timezone e.g. EST"
```
removedInput schema / properties / to_tz / title
```
Removed value: -"To Tz"
```

removedInput schema / title

Removed value: -"convert_timezoneArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "convert_timezoneOutput",
-  "type": "object"
-}New value: +null

First observedJul 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing: no DST handling, no output format, no note that timestamp defaults to now, no statement about invalid timezone behavior. 'Any timezones' is the only scope hint.

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?

A single front-loaded sentence with zero padding that communicates the essential operation. It is efficient, though the extreme brevity leaves important details unstated.

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?

For a simple utility this is roughly adequate, but with no output schema and no annotations the description should state the return shape and DST/default behavior. The gaps are not severe for a 3-param converter but leave the agent guessing on output.

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 all three parameters (to_tz, from_tz, timestamp) are already documented in the schema with examples. The description adds no syntax, format, or edge-case detail beyond that baseline.

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?

States a specific verb (Convert) and resource (timestamps between timezones), so the core function is unambiguous. However, it does nothing to distinguish itself from the near-identical sibling 'convert_timestamp', which an agent must disambiguate against.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no prerequisites, and no mention of the close alternative convert_timestamp. The agent is left to infer when this tool beats its sibling.

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

All GadgetHumans API Hub 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?