Skip to main content
Glama

time_now

Read-only

Get the current date and time across UTC, Unix, and selected time zones, including weekday, ISO week, and DST status. Use it to avoid guessing today's date.

Instructions

Current date/time (weekday, ISO week, DST), UTC, unix, other zones. Use instead of guessing today.

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_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezonesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.4/5.0
Behavior3/5

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

With readOnlyHint=true the safety profile is already covered, and the parenthetical adds real value by disclosing returned fields (weekday, ISO week, DST, UTC, unix) despite there being no output schema. It does not state what happens when timezones is omitted (no zones returned vs. local appended) or the format of zone strings, leaving a behavioral 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?

A single dense fragment, front-loaded with the resource and its returned facets, with zero filler. The telegraphic style borders on under-specification but nothing is wasted.

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 low-complexity read tool with no output schema, listing the returned facets is the right move and largely covers it. The missing pieces are the default behavior with no timezones supplied and the accepted timezone string format, which an agent must guess.

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 0% for the single optional timezones parameter; 'other zones' hints that it adds zones beyond UTC/unix, but gives no syntax hint (IANA names) or behavior for invalid zones. It adds marginal meaning over the bare array-of-strings 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 names the resource (current date/time) and enumerates the returned facets: weekday, ISO week, DST, UTC, unix, other zones. It is a fragment rather than a verb phrase, and it does not explicitly differentiate itself from the sibling time_convert, so it stops short of 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 Guidelines3/5

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

'Use instead of guessing today' gives a clear situational trigger for calling the tool, which is genuinely useful guidance. However, it never states when not to use it or points to time_convert for date arithmetic, so the alternative-routing is left to inference.

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