findtime.io MCP Server

Convert a time

convert_time

Read-onlyIdempotent

Converts a source timezone local time into one or more target locations. Requires structured from, to, and time fields. Whole-sentence questions are not location values. Unknown or ambiguous cities return clarification candidates. date accepts ISO YYYY-MM-DD, and time may include a simple human date phrase such as "3pm Tuesday". The result includes authoritative localTime.weekday, localTime.date, localTime.time12h/time24h, timezone abbreviation, and UTC offset for each location.

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": {
      "from": "<from>",
      "to": "<to>",
      "time": "<time>"
    },
    "name": "convert_time"
  }
}

Input Schema

Name	Required	Description
`to`	Yes
`date`	No	Optional date context. Accepts ISO YYYY-MM-DD or simple human values such as "Thursday", "tomorrow", or "next Friday".
`from`	Yes	Source location or timezone.
`time`	Yes	Source local time, such as "9:00 AM"; may include a simple human date phrase such as "3pm Tuesday".
`_endUserId`	No	Optional 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.
`toCountryCodes`	No
`fromCountryCode`	No	Optional ISO country hint for the source location.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral detail beyond annotations: unknown or ambiguous cities return clarification candidates, and the result includes authoritative local time fields, timezone abbreviation, and UTC offset for each location.

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 definition is front-loaded with the conversion purpose and then moves through required inputs, edge-case behavior, and return fields. It is reasonably concise, though a few sentences duplicate schema-level details.

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?

With no output schema, the description appropriately states what the result includes: localTime.weekday, date, 12h/24h time, timezone abbreviation, and UTC offset. It also covers ambiguity handling, though it does not discuss the optional country-code hints or multi-target expansion behavior in depth.

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?

The description explains the core from, to, time, and date semantics, including date and time formats, but much of that overlaps with the schema. It does not explain the optional country-code hint parameters, and with 71% schema description coverage the schema already carries most parameter documentation.

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 states a specific verb and resource: it converts a source timezone local time into one or more target locations. It distinguishes the tool from question-answering siblings by warning that whole-sentence questions are not location values, and it names concrete inputs and outputs.

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

Usage Guidelines4/5

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

It clearly establishes the usage context: structured from, to, and time fields are required, and natural-language questions should not be passed as location values. However, it does not explicitly name the preferred alternative such as answer_time_question when a whole-sentence question is supplied.

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 tools Inspect

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.