@findtime/mcp-server

time_snapshot

Read-onlyIdempotent

Returns current time snapshot payloads for one or multiple locations, with optional timezone transition details.

Instructions

Return the production time snapshot payload for one location or a list of locations.

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

Input Schema

Name	Required	Description
`query`	No	Single location query such as "Tokyo" or "Europe/London".
`locations`	No
`_endUserId`	No	Optional 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.
`countryCode`	No	Optional ISO country hint for a single query.
`countryCodes`	No
`includeTransitions`	No	Include last and next timezone transition details.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.27.0Aug 21, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the annotations: it does not explain what the 'snapshot payload' contains, whether results are cached, how errors are surfaced, or any rate 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?

The description is a single front-loaded sentence with no wasted words. It is appropriately concise, though its brevity contributes to gaps covered in other dimensions.

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?

With six optional parameters, no output schema, and many sibling time-related tools, the description is too thin. It does not describe the return shape of the snapshot payload or explain how the tool differs from siblings, leaving an agent with insufficient context to select and call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is moderate at 67%, and the description adds no parameter-level meaning beyond what the schema already provides. It does not clarify the relationship between query and locations, how countryCodes align with locations, or what includeTransitions changes in the payload.

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?

The description has a clear verb ('Return') and resource ('production time snapshot payload') and scopes it to one location or a list of locations. However, it does not distinguish this tool from siblings like get_current_time or convert_time, and the phrase 'production time snapshot payload' is somewhat opaque.

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 states the input scope (one location or a list) but gives no guidance on when to use this tool instead of alternatives such as get_current_time, search_timezones, or convert_time. There are no exclusions, prerequisites, or usage contexts.

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

Deploy Server