MCP-ADAPTER

time_convert

Convert date/time values between timezones from ISO 8601, Unix timestamps, 'now', or 'today' into a chosen target timezone.

Instructions

Convert a date/time between timezones. Accepts ISO 8601, unix timestamps, 'now', 'today'.

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

Input Schema

Name	Required	Default
`format`	No
`datetime`	Yes
`to_timezone`	No	UTC
`from_timezone`	No	UTC

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add real value by disclosing accepted input forms (ISO 8601, unix timestamps, 'now', 'today'), which is behaviorally meaningful. It says nothing about DST handling, invalid timezone behavior, or how the optional format string affects output, leaving core behavior undisclosed.

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, zero filler, with the core action front-loaded and the input-format detail immediately after. Nothing is redundant or padding.

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?

An output schema exists, so return values need not be explained, and the required datetime parameter is covered. Still, with zero annotations and zero schema coverage, the undefined format parameter, timezone identifier convention, and DST/error behavior leave the definition thinner than a 4-parameter conversion tool warrants.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters, so the description must compensate. It documents the datetime parameter's accepted formats well, and 'between timezones' weakly implies from_timezone/to_timezone, but the format parameter is never mentioned and no defaults or timezone identifier syntax (IANA name vs. offset) are given.

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 date/time between timezones.' That is unambiguous about the operation. However, it does not differentiate itself from adjacent siblings such as time_format, time_unix, or time_world_clock, so an agent must still infer which is the right pick for a given request.

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?

There is no explicit when-to-use, when-not-to-use, or alternative tool guidance. The description implies a timezone-conversion context but never says how it relates to time_format or time_world_clock, which overlap in domain. The input-format list is parameter information, not usage guidance.

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