Skip to main content
Glama

Convert Time

convert_time
Read-onlyIdempotent

Convert timestamps between time zones or switch between epoch and ISO-8601 formats.

Instructions

Convert a timestamp between time zones or between epoch and ISO-8601 formats.

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_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoISO time string
timezoneNoTarget timezone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds only that conversion can happen in either of two directions, and says nothing about the output representation (ISO string vs. epoch) or what happens when inputs are omitted. Useful but not rich behavioral context.

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?

One sentence, front-loaded with the verb and resource, with both supported modes enumerated. No filler, no restatement of the title.

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 tool is simple and its annotations are rich, but with no output schema the description should state what a conversion returns (an ISO string? an epoch number?) and what the defaults are when 'time' or 'timezone' is omitted. Those omissions matter for an agent that must consume the result.

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 the schema itself documents both parameters and the baseline is 3. The description adds no meaning beyond it, and it introduces a gap: it promises conversion 'between time zones' while the schema exposes only a target 'timezone' with no source zone, and all parameters are optional with no stated defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Convert) and resource (a timestamp) plus the two distinct conversion modes handled: time zone translation and epoch/ISO-8601 format translation. Nothing in the sibling list (code analysis, file ops, DB schema tools) overlaps, so an agent can immediately place this tool.

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 purpose implies when to reach for it, but there is no explicit when-to-use, no exclusions, and no mention of alternatives (e.g. formatting vs. arithmetic on timestamps). For a small utility tool this is adequate but leaves the agent to infer the trigger condition.

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