Skip to main content
Glama

Convert time zone

bursia_timezone_convert
Read-onlyIdempotent

Show a date/time in another IANA time zone (e.g. America/Bogota). Pure computation, free.

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>",
      "timeZone": "<timeZone>"
    },
    "name": "bursia_timezone_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
datetimeYesAn ISO 8601 datetime, e.g. 2026-10-30T12:00:00Z.
timeZoneYesIANA time zone, e.g. America/Bogota or Europe/Madrid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / datetime / description
      Added value: +"An ISO 8601 datetime, e.g. 2026-10-30T12:00:00Z."
    • addedInput schema / properties / timeZone / description
      Added value: +"IANA time zone, e.g. America/Bogota or Europe/Madrid."
  2. First observed

TDQS

A3.6/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 the safety profile is covered. The description adds only the cost/offline signal ('pure computation, free'), which is genuinely useful but thin; it says nothing about DST edge cases, ambiguous local times, or output format.

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 fragments with zero waste; the core operation is front-loaded before the cost aside. Nothing could be trimmed without losing information.

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 two-parameter, fully documented, annotation-covered tool this is close to sufficient, and the return value (a datetime rendered in the target zone) is easily inferred. The absence of an output schema means the exact output format is left implicit, which is the only real gap.

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%, and the schema already supplies the ISO 8601 example and the IANA zone examples that the description repeats. The description adds no semantics beyond the schema, 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?

States a specific verb ('Show') and resource ('a date/time in another IANA time zone'), so an agent immediately knows it is a rendering/conversion operation rather than a parser or epoch converter. It does not name the closest sibling, bursia_timestamp_convert, which is the one an agent could plausibly confuse it with.

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 phrase 'Pure computation, free' hints that this is a safe, no-cost lookup, but there is no explicit when-to-use or when-not-to-use guidance and no routing away from bursia_timestamp_convert. Usage is only implied by the purpose statement.

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