Skip to main content
Glama
Sign In

findtime.io MCP Server

by io.github.hkchao
OverviewDiscussionsAdmin

Get a daylight saving schedule

get_dst_schedule
Read-onlyIdempotent

Returns daylight saving schedules, current abbreviations, and transition details for a city or time zone. An explicit year selects transitions for that civil year; at sets the reference instant. This endpoint accepts structured location, year, and timestamp fields rather than relative-date questions.

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. Accepts a non-PII hash or token, excluding raw email addresses, names, or platform user IDs.
countryCodeNoOptional ISO country hint for ambiguous city names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The description adds the meaningful semantics of year ('selects transitions for that civil year') versus at ('sets the reference instant'), but says nothing about defaults, error cases, or limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the return payload and followed by the two semantics that matter. No filler, though the final sentence is slightly repetitive of the input-schema descriptions.

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?

Seven parameters with zero required fields create a real ambiguity the description does not resolve: what happens when all location fields are omitted, and which of city/timezone/query wins if several are supplied. Return contents are adequately previewed, which compensates for the missing output schema.

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 the baseline is 3. The description does add real value by clarifying the interaction between year and at, but it omits the precedence among city, timezone, and query, and never mentions countryCode or _endUserId.

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 ('Returns daylight saving schedules...transition details for a city or time zone'), which is clearly distinct from timezone search or time conversion siblings. The closing clause begins to differentiate it from question-answering tools but never names one.

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?

'This endpoint accepts structured location, year, and timestamp fields rather than relative-date questions' implies the boundary with answer_time_question but does not name it or state the selection rule. There is no explicit when-to-use or exclusion statement.

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

All findtime.io MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources