Skip to main content
Glama
Sign In
TimezoneToolkit MCP Server

TimezoneToolkit MCP Server

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calculate_countdown

Calculate the exact time remaining until a specified date or event. Provide the target date and optional timezone to get an accurate countdown.

Instructions

Calculate time remaining until a specific date/event

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": {
      "targetDate": "<targetDate>"
    },
    "name": "calculate_countdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoTitle or name of the event (optional)
timezoneNoIANA timezone name (e.g., 'America/New_York'). Defaults to system timezone.
targetDateYesTarget date/time (ISO string or natural language)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits, but it only says 'calculate time remaining' without explaining the output format, handling of past dates, precision, or timezone impact. This leaves significant ambiguity for the agent.

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 words. It earns its place by clearly stating the core function without bloat.

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?

Given the lack of an output schema and annotations, the description fails to explain the return value (e.g., days vs seconds, negative values for past dates) or any edge cases. A simple tool still requires this essential context to be used correctly.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The tool description adds no extra semantic meaning beyond what the schema already provides, but it does not conflict with it.

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 clearly states the tool's function with a specific verb ('Calculate') and a specific resource ('time remaining until a specific date/event'). This distinguishes it from sibling tools that handle conversions, current time, or related calculations.

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 description gives no guidance on when to use this tool versus its time-related siblings, nor any exclusions or alternatives. It simply restates the basic functionality without contextual cues.

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