Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Timezone, current time converter: time zone conversion

time
Read-only

The exact current date and time in any IANA time zone (UTC when none is given), with UTC offset, weekday, abbreviation and Unix timestamp, daylight saving time handled. Optionally convert a given moment into up to 10 other time zones in the same call. Use when an agent needs to know what time it is, to schedule across time zones or to turn a timestamp into local time. A bare GET is the smallest paid end-to-end test of an x402 or MPP client. Example: zone=Europe/Stockholm. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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
atNoOptional moment to convert, as ISO 8601 with an offset (default: now)
toNoOptional comma-separated time zones to convert the same moment into (max 10)
zoneNoIANA time zone name, e.g. Europe/Stockholm or America/New_York (default UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: pricing ($0.01/call, first 25 free, failed calls free), the payment paths (x402 USDC or card key), the fact that calls are billed per invocation so repeats are not free — which explains the idempotentHint=false annotation — and that DST is handled and nothing is mutated. The 'bare GET as smallest paid end-to-end test' note further signals it as a low-risk payment-path smoke test.

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?

Purpose and return fields are front-loaded, then usage, then pricing. Most sentences earn their place, but pricing is stated twice ('$0.01/call ... first 25 free' and 'each call is charged, so repeats are not free') and the x402/MPP smoke-test remark is somewhat tangential padding.

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?

With no output schema, the description carries the return-value burden and does so by enumerating offset, weekday, abbreviation and Unix timestamp. It also covers the optional conversion behavior and the billing model, leaving nothing an agent needs before calling.

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 schema already documents zone, at, and to, including the max-10 limit and ISO 8601-with-offset requirement. The description reinforces the UTC default and gives a zone example, but adds little syntax or semantic detail the schema lacks; 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?

States a concrete verb and resource: returns the exact current date/time in any IANA zone, with UTC default, offset, weekday, abbreviation and Unix timestamp, plus an optional multi-zone conversion of a given moment. There is no sibling time tool to confuse it with, and the scope (current time + conversion) is unmistakable.

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?

Explicitly names the triggering situations: needing to know the current time, scheduling across time zones, or turning a timestamp into local time. It does not state when NOT to use it (e.g. pure arithmetic between two zones) and names no alternative, but the positive guidance is clear and concrete.

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.