Skip to main content
Glama
Sign In

mcp-time

by io.github.mcpcentral-io
OverviewDiscussionsAdmin

Get Timestamp

get_timestamp

Converts a date-time string to a Unix timestamp in milliseconds.

Input Schema

NameRequiredDescriptionDefault
timeNoThe time to convert. Format: YYYY-MM-DD HH:mm:ss

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / time / description
      Previous value: -"The time to convert (format: YYYY-MM-DD HH:mm:ss). Defaults to current time"New value: +"The time to convert. Format: YYYY-MM-DD HH:mm:ss"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "timestamp": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "timestamp"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed4 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / time / description
      Previous value: -"The time to convert. Format: YYYY-MM-DD HH:mm:ss"New value: +"The time to convert (format: YYYY-MM-DD HH:mm:ss). Defaults to current time"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "timestamp": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "timestamp"
+  ],
+  "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?

With no annotations, the description carries the full behavioral burden. It usefully discloses the output unit (milliseconds), but a timestamp conversion hinge on timezone handling (UTC vs local) and behavior on null/unparsable input, neither of which is stated — a real gap for the only parameter, which has no default despite being non-required.

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?

One front-loaded sentence with zero waste. It is efficient, though the brevity leaves too much unsaid rather than being over-optimized.

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 one-parameter pure-conversion tool with a fully described schema, this is close to adequate. The absence of timezone semantics and default-input behavior leaves a meaningful gap an agent would want resolved before invoking.

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 single parameter is fully documented with its format in the schema, so the baseline is 3. The description adds nothing beyond restating the input type, and does not clarify what a missing non-required 'time' value does.

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 specific verb and transformation ('Converts a date-time string to a Unix timestamp in milliseconds'), so the input and output types are unambiguous. However, it does not differentiate itself from the sibling 'convert_time', which plausibly does the same conversion, leaving the agent to guess which one to pick.

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?

No guidance on when to use this rather than 'convert_time', 'relative_time', or 'current_time'. The description gives no context, prerequisites, or exclusions at all.

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