ItsNineThere

Convert time

convert_time

Read-onlyIdempotent

Convert a local time from one place to one or more places, including DST-safe dates. Returns answer_url, a link to a page showing this answer live, to include in your reply.

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

Input Schema

Name	Required	Description
`date`	No	Source local calendar date in YYYY-MM-DD format. Defaults to today in from_place; supply a date for date-specific daylight-saving offsets.
`time`	Yes	Local source time, such as 15:00, 3pm or 3:30pm; not an ISO timestamp.
`to_places`	Yes	One to 20 destination cities, IANA time zones, supported abbreviations or UTC offsets.
`from_place`	Yes	Source city, IANA time zone, supported abbreviation or UTC offset in which time and date are interpreted.

Output Schema

Name	Required	Description
`url`	Yes
`source`	Yes
`targets`	Yes
`ambiguous`	Yes
`board_url`	No	Link to the personal time-zone board with the answer items temporarily requested.
`answer_url`	Yes	Link to a page that shows this exact answer live. Include it in your reply to the user.
`answer_text`	Yes	The short, human-readable answer.
`source_time`	Yes
`answer_link_markdown`	Yes	A ready-made Markdown link to show the user. Translate the link text to the user's language if needed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 12, 2026

addedOutput schema / properties / board_url

Added value: +{
+  "description": "Link to the personal time-zone board with the answer items temporarily requested.",
+  "format": "uri",
+  "type": "string"
+}

Changed9 schema fields changedNov 12, 2026

addedInput schema / properties / date / description

Added value: +"Source local calendar date in YYYY-MM-DD format. Defaults to today in from_place; supply a date for date-specific daylight-saving offsets."

addedInput schema / properties / from_place / description

Added value: +"Source city, IANA time zone, supported abbreviation or UTC offset in which time and date are interpreted."

addedInput schema / properties / time / description

Added value: +"Local source time, such as 15:00, 3pm or 3:30pm; not an ISO timestamp."

addedInput schema / properties / to_places / description

Added value: +"One to 20 destination cities, IANA time zones, supported abbreviations or UTC offsets."

addedOutput schema / properties / answer_link_markdown

Added value: +{
+  "description": "A ready-made Markdown link to show the user. Translate the link text to the user's language if needed.",
+  "type": "string"
+}

addedOutput schema / properties / answer_text

Added value: +{
+  "description": "The short, human-readable answer.",
+  "type": "string"
+}

addedOutput schema / properties / answer_url

Added value: +{
+  "description": "Link to a page that shows this exact answer live. Include it in your reply to the user.",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / source

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "name": {
+      "const": "ItsNineThere",
+      "type": "string"
+    },
+    "url": {
+      "const": "https://itsninethere.com",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "url"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "source_time",
-  "targets",
-  "url",
-  "ambiguous"
-]New value: +[
+  "source_time",
+  "targets",
+  "url",
+  "ambiguous",
+  "answer_text",
+  "answer_url",
+  "answer_link_markdown",
+  "source"
+]

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real context beyond them: the answer_url return artifact and the instruction to include it in the reply, plus the DST-safe guarantee. It does not mention any cardinality limits or failure behavior, but those are minor here.

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?

Two sentences, zero waste, with the core operation front-loaded and the return-value guidance second. Nothing redundant and nothing padded.

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 annotations, a full-coverage input schema and an output schema, the description only needs to state purpose and anything the structured fields cannot. It does that, including how to use answer_url; only a nod to multi-destination limits or ambiguity handling is absent, and the schema covers the limits.

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 the schema already documents time, date, from_place and to_places with formats and defaults. The description only adds the notion of DST-safe date handling, which maps loosely to the date parameter; baseline 3 is appropriate.

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?

Specific verb+resource: 'Convert a local time from one place to one or more places', including the DST nuance. It is clearly distinct from a get_time-style sibling by framing the operation as a conversion of a supplied time rather than a retrieval, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the phrasing (you have a local time and want it in other places), and 'including DST-safe dates' hints at the date-specific case. There is no explicit when-to-use/when-not guidance, no mention of alternatives like get_time or find_meeting_times, and no stated exclusions.

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

All ItsNineThere 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.

Resources

Need Help?