Skip to main content
Glama

Convert time

time_convert

Convert a civil time from one IANA time zone to another using Intl. Does not call the network.

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>",
      "from_tz": "<from_tz>",
      "to_tz": "<to_tz>"
    },
    "name": "time_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesYYYY-MM-DDTHH:mm in from_tz, or an ISO timestamp.
to_tzYesIANA time zone to convert to.
from_tzYesIANA time zone the time is in.

Output Schema

NameRequiredDescriptionDefault
okNo
toNo
utcNo
fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose one real trait: it is a local Intl computation with no network call, implying a pure, side-effect-free operation. It says nothing about DST ambiguity/gap handling, invalid-zone errors, or whether it depends on the runtime's ICU data, which matters for a time-zone tool.

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 action and resource, with the network caveat as a compact qualifier. Nothing is redundant or padded.

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 three-parameter pure conversion with a full output schema, the definition covers purpose, input format, and the no-network trait, so an agent has enough to call it correctly. The remaining gap is edge-case behavior (DST gaps, invalid zone IDs), which is minor but would be valuable given zero annotations.

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 (time, from_tz, to_tz) are already documented in the schema. The description's phrase "civil time" reinforces the expected input format but adds no syntax, format, or edge-case detail beyond what the schema states, so the baseline 3 applies.

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 gives a specific verb and resource ("Convert a civil time") plus the domain constraint ("from one IANA time zone to another"), so an agent knows exactly what it does. It stops short of naming a sibling like date_math or time to clarify the boundary, which keeps it from a 5.

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?

Usage is only implied: the tool obviously applies when shifting a timestamp between zones, but there is no explicit when-to-use, when-not, or pointer to date_math/time for related arithmetic or clock-reading needs. The "does not call the network" note is behavioral, not routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources