Skip to main content
Glama

Current time in a time zone

time_now

Use when an agent must stamp or schedule something in a particular place and needs every form at once: ISO with offset, 24-hour, 12-hour, weekday, unix timestamp and UTC. It also says whether daylight saving is active right now and what the zone's standard offset is, so a shifted clock can be told apart from a permanent one. $0.002 per call, paid over x402 (USDC).

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": {
      "zone": "<zone>"
    },
    "name": "time_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYesIANA time zone, e.g. "Asia/Tokyo" or "UTC". Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the complete return surface, that DST status and standard offset are reported so a shifted clock can be distinguished from a permanent offset, and the cost/auth model ($0.002 per call paid over x402 in USDC). It omits failure behavior for an invalid IANA zone string, which is the main remaining gap.

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?

Two sentences, front-loaded with the usage trigger followed by the output inventory and pricing, with no filler. The clause explaining why offset and DST are both returned ('so a shifted clock can be told apart from a permanent one') is somewhat verbose but earns its place by justifying the extra fields.

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 simple single-parameter read tool with no output schema, and the description compensates by enumerating the returned fields, the DST/offset nuance, and the paid x402 cost model. Only the invalid-zone error path is unaddressed, a minor omission for a tool of this complexity.

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?

There is only one parameter and schema coverage is 100%, with the schema itself giving the IANA format and examples. The description adds no format or edge-case detail beyond 'a particular place', so the baseline 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 states a specific verb and resource – return the current time in a named zone – and enumerates the exact output forms (ISO with offset, 24-hour, 12-hour, weekday, unix timestamp, UTC) plus DST and standard-offset flags. It implicitly separates itself from time_convert/time_zones by emphasizing 'now' and 'every form at once', but never names those siblings, so an agent must infer the boundary.

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?

The opening clause 'Use when an agent must stamp or schedule something in a particular place' gives a concrete triggering condition rather than a generic 'get time'. It does not state when NOT to use it or point to time_convert/time_zones for conversion or zone-listing tasks, so the routing guidance is clear but not exhaustive.

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