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

@findtime/mcp-server

by hkchao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_location_by_id

Read-onlyIdempotent

Retrieves the exact production location record for a stable findtime ID returned by timezone search, resolving older IDs to the original city.

Instructions

Hydrate an exact production location record by stable findtime id returned from search_timezones. Do not invent ids. If search_timezones has not been called, call it first.

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": {
      "id": "<id>"
    },
    "name": "get_location_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStable location id. Current records use findtime:slug|CC|geonameId-or-state|TZ. Older findtime:slug|CC|TZ ids still resolve to the original city.
_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.28.1
    • changedInput schema / properties / id / description
      Previous value: -"Stable location id such as \"findtime:victoria|CA|America/Vancouver\"."New value: +"Stable location id. Current records use findtime:slug|CC|geonameId-or-state|TZ. Older findtime:slug|CC|TZ ids still resolve to the original city."
  2. First observedv3.27.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real workflow context — that ids must originate from search_timezones and must not be fabricated — but says nothing about failure behavior or what a hydrated record actually contains.

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 verb and resource, then the prerequisite, with zero hedging or repetition. Every sentence carries an actionable instruction.

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 single-param, read-only lookup with full annotation coverage this is nearly complete: it tells the agent what it fetches and where the key comes from. The remaining gap is that with no output schema, nothing states which fields the returned location record exposes, so the agent cannot anticipate the payload.

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

Parameters4/5

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

Schema coverage is 100% and the id property already documents the format and legacy-id fallback, so the baseline is 3. The description earns one above baseline by stating the provenance of the id value (it must come from search_timezones), which the schema does not say.

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?

Names a specific verb ("Hydrate") and resource ("exact production location record") keyed by a stable id, and explicitly ties itself to search_timezones as the id source, which separates it from that sibling without opening either 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?

Gives an explicit gating condition ("If search_timezones has not been called, call it first") and an explicit prohibition ("Do not invent ids"), which is exactly the when-to-use / how-not-to-use guidance an agent needs for a lookup tool.

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