Skip to main content
Glama
Sign In

mcp-time

by io.github.mcpcentral-io
OverviewDiscussionsAdmin

Get Current Time

current_time

Returns the current time in UTC and a specified or guessed timezone.

Input Schema

NameRequiredDescriptionDefault
formatNoThe format for the returned time string. Either a dayjs token string (e.g. "YYYY-MM-DD HH:mm:ss") or a named format: "iso8601" / "rfc3339" (ISO 8601 UTC), "unix" (epoch seconds), "unix_ms" (epoch milliseconds).YYYY-MM-DD HH:mm:ss
timezoneNoThe IANA timezone name (e.g., "America/New_York"). Defaults to the server's guessed timezone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / format / default
      Added value: +"YYYY-MM-DD HH:mm:ss"
    • changedInput schema / properties / format / description
      Previous value: -"Format for the returned time string (default YYYY-MM-DD HH:mm:ss)"New value: +"The format for the returned time string. Either a dayjs token string (e.g. \"YYYY-MM-DD HH:mm:ss\") or a named format: \"iso8601\" / \"rfc3339\" (ISO 8601 UTC), \"unix\" (epoch seconds), \"unix_ms\" (epoch milliseconds)."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone name (e.g., \"America/New_York\"). Defaults to the server's guessed timezone"New value: +"The IANA timezone name (e.g., \"America/New_York\"). Defaults to the server's guessed timezone."
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "localTime": {
-      "type": "string"
-    },
-    "timezone": {
-      "type": "string"
-    },
-    "utcTime": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "utcTime",
-    "localTime",
-    "timezone"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed6 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / format / default
      Removed value: -"YYYY-MM-DD HH:mm:ss"
    • changedInput schema / properties / format / description
      Previous value: -"The format for the returned time string."New value: +"Format for the returned time string (default YYYY-MM-DD HH:mm:ss)"
    • changedInput schema / properties / timezone / description
      Previous value: -"The IANA timezone name (e.g., \"America/New_York\"). Defaults to the server's guessed timezone."New value: +"IANA timezone name (e.g., \"America/New_York\"). Defaults to the server's guessed timezone"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "localTime": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "string"
+    },
+    "utcTime": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "utcTime",
+    "localTime",
+    "timezone"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one real behavioral trait — that the timezone falls back to a server-side guess when unspecified — but says nothing about invalid timezone handling, error behavior, or output characteristics.

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?

A single front-loaded sentence with no filler. Slightly loose phrasing ('in UTC and a specified or guessed timezone') introduces a small ambiguity about what the returned string actually contains.

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?

This is a zero-required-parameter read tool with a fully documented schema and no output schema, so the description is nearly sufficient as-is. Only the missing differentiation from sibling time tools is a notable gap.

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 both parameters (format, timezone) are already fully documented with named formats and IANA examples. The description's mention of 'specified or guessed timezone' adds marginal context but no syntax or format detail beyond the schema.

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 states a specific verb (Returns) and resource (the current time) with the output basis (UTC plus a specified or guessed timezone), which is clear enough to act on. It does not differentiate itself from siblings like get_timestamp or relative_time, which is the only thing keeping it from a 5.

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 guidance on when to use this tool versus the five siblings (convert_time, get_timestamp, relative_time, etc.), and no mention of exclusions or prerequisites. Usage is only inferable from the purpose statement.

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

All mcp-time 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