Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

time_convert

Convert a time between IANA timezones and return the UTC offset for each. Pure CPU, instant.

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": {
      "time": "<time>"
    },
    "name": "time_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget timezone
fromNoSource timezone
timeYesTime or timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Source timezone",
+  "type": "string"
+}
    • addedInput schema / properties / time
      Added value: +{
+  "description": "Time or timestamp",
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Target timezone",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "time"
+]
  4. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two useful behavioral traits — deterministic local computation ("Pure CPU, instant") and that a UTC offset is returned for each zone — but says nothing about defaults when `from`/`to` are omitted, accepted time input formats, or failure behavior for invalid zone identifiers.

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?

Two short sentences, front-loaded with the core action and output, then a one-clause cost/behavior note. Nothing is wasted and nothing is buried.

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 three-parameter tool with full schema coverage and no output schema, the description covers purpose, zone format and return shape. It is still incomplete on the practical details an agent needs before calling — default zone behavior for the optional `from`/`to` and the accepted format of `time`.

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, and the description earns an increment by constraining the vague schema labels ("Source timezone"/"Target timezone") to IANA identifiers and by clarifying that both the converted time and per-zone UTC offsets come back. It still does not address how the loosely specified "Time or timestamp" string is parsed.

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 and resource ("Convert a time between IANA timezones") plus the return content ("UTC offset for each"). It does not, however, distinguish itself from the several timezone-related siblings (convert_timezone, convert_timestamp, timezone, timestamp), so an agent cannot tell from the description alone which one to pick.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. With convert_timezone, convert_timestamp, timezone and timestamp all present in the sibling list, the absence of any routing guidance is a real gap.

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 toolsInspect
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