Skip to main content
Glama
Sign In
TimezoneToolkit MCP Server

TimezoneToolkit MCP Server

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calculate_timezone_difference

Calculate the time difference between any two IANA timezones. Provide source and target timezone names to get the offset.

Instructions

Calculate the time difference between two timezones

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": {
      "fromTimezone": "<fromTimezone>",
      "toTimezone": "<toTimezone>"
    },
    "name": "calculate_timezone_difference"
  }
}

Input Schema

NameRequiredDescriptionDefault
toTimezoneYesTarget IANA timezone name (e.g., 'Europe/London')
fromTimezoneYesSource IANA timezone name (e.g., 'America/New_York')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It merely restates the tool's name/function without explaining key behaviors such as whether DST is considered, whether the result is a decimal number of hours, or whether the difference depends on the current date. This is a minimal statement with no added 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?

The description is a single, concise sentence with no redundant content. It is front-loaded with the main action and resource, making it easy to skim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (2 parameters, no nested objects) but there is no output schema, so the description should clarify what is returned. It does not mention the return format, units, or DST handling. Given the lack of annotations and output schema, the description is incomplete for a fully informed agent.

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% for both parameters, with clear examples of IANA timezone names. The description text adds no parameter information, but the schema already provides full clarity, so the baseline score of 3 is appropriate.

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?

The description uses the specific verb 'calculate' with the resource 'time difference between two timezones', clearly distinguishing it from siblings like convert_time, get_current_time, and list_timezones. It precisely states what the tool does.

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 description implies when to use the tool (when you need the time difference between timezones) but provides no explicit guidance on alternatives or exclusions. The context of sibling tools makes the purpose clear, but the description itself offers no comparison or when-not-to-use advice.

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

Deploy Server

Other Tools