Skip to main content
Glama
Sign In
@findtime/mcp-server

@findtime/mcp-server

by hkchao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_dst_schedule

Read-onlyIdempotent

Query daylight saving time transition dates and current timezone abbreviations by city, IANA timezone, or year, with an optional reference timestamp.

Instructions

Return the production DST schedule payload, including current abbreviation and transition details. For relative-date inputs ("this week", "next Friday", "tomorrow"), route to answer_time_question, which resolves the relative date and dispatches internally.

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": "get_dst_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoOptional ISO timestamp used as the reference instant.
cityNoCity name such as "Reykjavik".
yearNoOptional calendar year used to return DST transitions for that civil year.
queryNoFree-form location query.
timezoneNoDirect IANA timezone, such as "America/New_York".
_endUserIdNoOptional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID.
countryCodeNoOptional ISO country hint for ambiguous city names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.27.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered and the bar here is lower. The description contributes only the payload contents and the internal-dispatch behavior of the sibling; it says nothing about ambiguous-location handling or what happens when no location argument is supplied.

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 sentences, no filler, and the core capability is front-loaded before the routing caveat. Every clause carries information an agent can act on.

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?

With seven optional parameters, no required fields and no output schema, the description partially compensates by naming the payload's contents. It still leaves open the zero-argument behavior and how the four overlapping location parameters interact, which matters for a tool with this many inputs.

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 all seven parameters (including the host-populated _endUserId) are already documented in the schema, which sets the baseline at 3. The description adds no guidance on which of city/query/timezone/countryCode to prefer or whether any is required, so it does not exceed that baseline.

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 opens with a specific verb and resource ('Return the production DST schedule payload') and adds scope detail ('current abbreviation and transition details'), so an agent knows exactly what this yields. It also names a sibling, answer_time_question, which sets it apart from at least one neighboring tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not rule with the alternative: relative-date phrasing such as 'this week' or 'next Friday' must route to answer_time_question. That is concrete routing guidance, though it stays silent on how this differs from other absolute-time siblings like get_current_time or time_snapshot.

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