Query an NTP server for current UTC time and this clock's offset, and append the sample to the drift log. Call it periodically to build drift history.
| Name | Required | Description | Default |
|---|---|---|---|
| server | No | NTP server to query | time.cloudflare.com |
| timezone | No | IANA timezone for a 'local' field, e.g. America/New_York. Optional -- the HTTP transport also takes ?tz= in the URL. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the side effect (appending to the drift log) and the return of time and offset. This goes beyond basic intent but does not cover failure modes or prerequisites like network access, so it is good but not exhaustive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The primary purpose and the call frequency guidance are both front-loaded, making it easy for an agent to grasp the tool quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no output schema, the description covers the main behavior and side effect. It implies return values (UTC time and offset) but does not explain timezone handling beyond the schema. It also does not mention failure handling, which is minor for this context. Overall adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so both parameters are already documented. The description adds no extra meaning about the parameters, so it stays at the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool queries an NTP server for UTC time and clock offset, and appends to a drift log. This is a specific verb-resource pair that differentiates it from the sibling get_drift, which likely reads the log.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description advises calling it periodically to build drift history, which is clear usage context. However, it does not explicitly mention when not to use it or point to get_drift as the alternative for reading the drift log, so it misses the 'when-not' and alternative guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a completely distinct purpose: math evaluation, text diffing, UUID generation, time querying, and drift analysis. No overlap or ambiguity between them.
All tool names follow the verb_noun pattern (calculate, diff, generate_uuid, get_drift, get_time), providing a consistent and predictable naming convention.
With 5 tools, the server is well-scoped for a utility toolkit. Each tool serves a clear and distinct function, and the count feels neither sparse nor bloated.
The tool set covers a reasonable range of utility functions (math, text, ID, time), though it could benefit from a few more general-purpose operations (e.g., string handling or encoding) to be fully comprehensive for a utility server.