Skip to main content
Glama

Current time

time

Current UTC time, plus the same instant in an IANA time zone. Defaults to UTC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNoIANA time zone, for example America/New_York. Omit for UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load. It discloses that the call is a pure read of the current instant, that it always includes UTC regardless of the argument, and that omitting the argument falls back to UTC — enough to convey that there are no side effects, permissions, or rate concerns. It does not state the serialization format of the returned timestamp, which is the one remaining behavioral unknown.

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?

A single front-loaded sentence with zero filler; the primary result (UTC time) precedes the optional variation (IANA zone) and the default behavior.

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?

There is no output schema, so the description must describe the return value, and it does: both the UTC instant and the localized rendering. The only omission is the output format (e.g. ISO 8601 vs epoch), which is a small but real gap for a tool whose sole purpose is returning a timestamp.

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%, so the timezone parameter and its example are already fully documented in the schema. The description's 'Defaults to UTC' restates the schema's 'Omit for UTC' rather than adding new meaning. Baseline 3 applies.

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 names a specific resource (current time) and states exactly what is returned: the UTC instant plus the same instant rendered in an IANA time zone. It is unambiguous and cannot be confused with the sibling utilities (uuid, echo, whoami, ask).

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 only implied: the tool obviously exists to fetch the current time, and 'Defaults to UTC' hints that the timezone argument is optional. There is no explicit statement of when to use it versus any alternative, but for a trivial utility with no real alternatives that gap is minor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources