Skip to main content
Glama
Sign In

findtime.io MCP Server

by io.github.hkchao
OverviewDiscussionsAdmin

Get a location by ID

get_location_by_id
Read-onlyIdempotent

Returns an exact production location record for a stable findtime.io location identifier. The identifier refers to a record in the location catalog.

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. Accepts a non-PII hash or token, excluding raw email addresses, names, or platform user IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add the parts annotations can't. It contributes the useful fact that the lookup is 'exact' rather than fuzzy and that IDs point at catalog records, but says nothing about what happens on an unknown or legacy ID or what the returned record contains.

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?

Two short sentences, front-loaded with the outcome and with no filler. The second sentence is mildly redundant with the schema's id description, which keeps it from a 5.

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?

For a two-parameter lookup with full schema coverage and complete annotations, most of what an agent needs is present. The notable gap is that no output schema exists and 'location record' is never unpacked, so the agent cannot anticipate the returned fields or the not-found behavior.

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 coverage is 100% and the id property description already spells out the modern and legacy id formats in detail, plus the non-LLM _endUserId token. The description adds only the framing that the identifier resolves to a catalog record, so the baseline 3 applies.

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 concrete verb and resource: 'Returns an exact production location record', and qualifies the key domain ('findtime.io location identifier'), which is more specific than the title's restatement. It does not, however, explicitly distinguish itself from catalog/tz-related siblings such as search_timezones.

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?

There is no statement of when to reach for this tool versus search_timezones or any other lookup path, and no conditions or exclusions are given. At most the phrase 'for a stable ... identifier' hints that an ID must be in hand, which is inference rather than guidance.

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