Skip to main content
Glama

time_convert

Read-only

Convert times between time zones with DST and day-shift handling, or find the weekday and ISO week for a date.

Instructions

Convert a time between zones (DST-aware, day shifts); also weekday/ISO week of a date. Times: now, today, YYYY-MM-DD[ HH:MM], DD.MM.YYYY[ HH:MM], HH:MM, unix. Zones: IANA, city, CET/PST; default local.

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": "time_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description does add real behavioral context beyond that: DST-awareness and day-shift handling across zone boundaries, plus the range of accepted time syntaxes. It stops short of saying what comes back (string vs. structured breakdown) or how multiple target zones behave.

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?

Dense, front-loaded, and free of filler: one sentence states the primary action, a clause adds the secondary one, then two label-prefixed lists of accepted formats. The telegraphic style is efficient, though the format lists read as schema content that arguably belongs in parameter descriptions.

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, no-output-schema conversion tool, the description covers input formats well but leaves the return contract entirely unspecified and does not clarify the multi-zone array semantics. An agent could invoke it, but could not predict the result shape or handle the `to` array confidently.

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 0% across three parameters, so the description carries the whole burden for input syntax. It usefully enumerates accepted time and zone formats, but never binds those to parameter names — an agent still cannot tell from the text that `from` is the source zone, `to` is an array of targets, or that `time` defaults to now. Partial compensation only.

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 time between zones") plus a secondary capability ("weekday/ISO week of a date"), which is far more than a restatement of the name. It does not, however, contrast itself with plausible siblings such as time_now or date_diff, so an agent must infer the boundary.

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 text lists accepted input formats but never says when to prefer this tool over alternatives like time_now (even though "now" is listed as a valid input) or date_diff. There are no exclusions, prerequisites, or default-behavior guidance beyond "default local."

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