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

@findtime/mcp-server

by hkchao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_timezones

Read-onlyIdempotent

Disambiguate city, country, abbreviation, or timezone queries to obtain suggested queries and IDs for accurate time lookups and conversions.

Instructions

Disambiguate a city, country, abbreviation, or timezone before calling other tools. Use this when a lookup is unknown or ambiguous, then retry get_current_time, convert_time, or find_meeting_time with candidate.suggestedQuery, candidate.suggestedId, or countryCode. This does not return the current time.

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": {
      "query": "<query>"
    },
    "name": "search_timezones"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of search results to return.
queryYesSearch term such as "Victoria", "Sao Paulo", or "Tokyo".
_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 used for ranking and disambiguation. This is not a strict filter.
candidateLimitNoPage size for namesake candidates. Default 6. Follow moreCandidates.resolve or moreCandidates.search for the rest.
candidateOffsetNoSkip this many namesake candidates. Copy from moreCandidates.candidateOffset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.28.1
    • addedInput schema / properties / candidateLimit
      Added value: +{
+  "description": "Page size for namesake candidates. Default 6. Follow moreCandidates.resolve or moreCandidates.search for the rest.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / candidateOffset
      Added value: +{
+  "description": "Skip this many namesake candidates. Copy from moreCandidates.candidateOffset.",
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return."New value: +"Maximum number of search results to return."
  2. First observedv3.27.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds real value beyond that by naming the fields returned per candidate (suggestedQuery, suggestedId, countryCode) and clarifying the negative behavior ('does not return the current time'), which prevents a common misuse. It stops short of describing the overall response envelope or moreCandidates pagination behavior.

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?

Three short sentences, front-loaded with the purpose, then the trigger/retry path, then the explicit exclusion. Every clause earns its place and nothing is repeated from the schema.

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

Completeness4/5

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

For a six-parameter read-only search with full schema coverage and strong annotations, the description covers purpose, trigger, and the fields needed to continue the workflow. The only gap is the shape of the result set (candidates array, moreCandidates paging), which is referenced only indirectly through the schema's candidateLimit/candidateOffset hints.

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 six parameters are already documented, and the description adds little parameter-level meaning beyond confirming countryCode can be fed back into follow-up calls. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('Disambiguate a city, country, abbreviation, or timezone') and immediately distinguishes itself from siblings by stating 'This does not return the current time.' An agent can tell this is the resolver step rather than a time-query tool without opening any schema.

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

Usage Guidelines5/5

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

It states the exact trigger condition ('when a lookup is unknown or ambiguous') and the downstream flow: retry get_current_time, convert_time, or find_meeting_time with candidate.suggestedQuery, candidate.suggestedId, or countryCode. Both when-to-use and what-to-do-next are explicit, with named alternatives.

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