Skip to main content
Glama
MCP Server Starter

MCP Server Starter

by ninonorden

Current time in a time zone

time_in_zone
Read-onlyIdempotent

Returns the current date and time in a specified IANA time zone so users can check local time for a city or region.

Instructions

Returns the current date and time in the given IANA time zone (e.g. Europe/Amsterdam, America/New_York). Use it whenever the user asks what time it is somewhere.

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": {
      "timeZone": "<timeZone>"
    },
    "name": "time_in_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeZoneYesIANA time zone name, e.g. Asia/Tokyo

Output Schema

NameRequiredDescriptionDefault
isoYes
localYes
timeZoneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, so the safety profile is covered. The description contributes only the fact that the value is the *current* time and that the zone must be IANA-formatted. It does not mention what happens with an invalid or ambiguous zone name, nor any latency or caching behavior — acceptable given annotations, but thin.

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: the first says what it does and the accepted format, the second says when to call it. Nothing is repeated or padded, and the core purpose is front-loaded.

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?

With one required parameter, full schema coverage, and a dedicated output schema, the definition covers everything an agent needs to invoke it correctly. The only shortfall is that it says nothing about the failure mode for a malformed zone name, which would help an agent recover from errors.

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 parameter already documents the IANA format with an example (Asia/Tokyo). The description restates that with two more examples, which is mild reinforcement rather than new meaning — nothing about offsets, aliases, or UTC handling is added. Baseline 3 is appropriate.

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 current date and time") plus the exact input domain ("in the given IANA time zone") with format examples. An agent knows precisely what the call produces without opening the schema. No siblings exist, so no differentiation is required.

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 the user asks what time it is somewhere" gives an explicit, natural-language trigger condition tied to the parameter. There are no exclusions or alternatives listed, but the sibling list is empty, so there is nothing to route against.

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

Deploy Server

Other Tools