Skip to main content
Glama

Get the current time

get_current_time
Read-onlyIdempotent

Current date and time in UTC or any IANA timezone, with weekday, UTC offset and Unix time. Use it whenever you need to know the present moment.

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": "get_current_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNoIANA timezone name, e.g. Europe/Paris or America/New_York. Default UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered structurally. The description adds value by specifying the exact returned components (weekday, UTC offset, Unix time) and the timezone-default behavior, which annotations do not convey.

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 short sentences, front-loaded with the capability and followed by the trigger condition. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple zero-required-parameter read tool with rich annotations and full schema coverage needs little else. The description covers input scope and return contents, so an agent has everything required to call it correctly.

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 timezone parameter is fully documented with examples and the UTC default. The description restates the accepted input range (UTC or any IANA timezone) but adds no format or validation detail beyond the schema, so the baseline of 3 applies.

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 names a specific resource and scope: the current date and time in UTC or any IANA timezone, plus what comes back (weekday, offset, Unix time). An agent can immediately tell this apart from convert_time or compute_duration, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

"Use it whenever you need to know the present moment" gives a clear positive trigger for invocation. It stops short of stating when not to use it or pointing to conversion/duration siblings, so there is no explicit exclusion guidance.

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.