ItsNineThere

Get current time

get_time

Read-onlyIdempotent

Current time in one or more cities, time zones, abbreviations or UTC offsets. 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": {
      "places": "<places>"
    },
    "name": "get_time"
  }
}

Input Schema

Name	Required	Description	Default
`places`	Yes	One to 20 cities, IANA time zones, supported abbreviations or UTC offsets, for example Copenhagen, Europe/London or UTC+02:00.
`from_place`	No	Optional reference city, IANA time zone, abbreviation or UTC offset for difference_hours. Omit to return times without a reference comparison.

Output Schema

Name	Required	Description
`url`	Yes
`places`	Yes
`source`	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.
`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"
+}

Changed7 schema fields changedNov 12, 2026

addedInput schema / properties / from_place / description

Added value: +"Optional reference city, IANA time zone, abbreviation or UTC offset for difference_hours. Omit to return times without a reference comparison."

addedInput schema / properties / places / description

Added value: +"One to 20 cities, IANA time zones, supported abbreviations or UTC offsets, for example Copenhagen, Europe/London or UTC+02:00."

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: -[
-  "places",
-  "url"
-]New value: +[
+  "places",
+  "url",
+  "answer_text",
+  "answer_url",
+  "answer_link_markdown",
+  "source"
+]

First observedNov 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful context that the result includes answer_url, a live-answer link intended for reply inclusion, but it does not discuss other behavioral details such as error behavior for ambiguous places.

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?

The description is two tight sentences with the purpose front-loaded and the output-link instruction placed immediately after. There is no redundant or filler wording.

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 simple two-parameter lookup tool with full schema coverage, annotations, and an output schema, the description covers the essential purpose and the special answer_url output. The main remaining gap is usage guidance against siblings, which prevents a perfect score.

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 parameters are already fully documented with examples and constraints. The description restates the accepted place formats but adds no meaning beyond the schema, such as how from_place affects the result.

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?

The description clearly states the resource and scope: current time for one or more places, with accepted place formats. It is specific enough that an agent can distinguish a current-time lookup from conversion or meeting tools, though it does not explicitly name or contrast any sibling.

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?

The description implies usage by saying it returns current times, but gives no explicit when-to-use guidance or exclusions relative to alternatives such as convert_time or find_meeting_times. No conditions for choosing this tool over another are stated.

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?