Current time in a named IANA timezone.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | HTTPS URL to normalize or cite | |
| host | No | Public hostname | |
| json | No | JSON text to validate; discarded after the check | |
| zone | No | IANA timezone name |
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 provided, the description carries the full burden of disclosing behavior. It implies a read-only operation by stating 'current time', but does not explicitly mention side effects, permissions, or the fact that it is safe. The mismatch between the description and the schema parameters (url, host, json) further muddies the expected behavior.
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?
The description is a single, concise sentence that conveys the core functionality without unnecessary words. It is well-structured and easy to parse.
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?
The description is too brief to explain the presence of multiple parameters (url, host, json) that seem unrelated to timezone lookups. It lacks context about why these parameters exist or how they interact with the primary operation, leaving gaps in understanding for an agent.
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?
The schema provides descriptions for all parameters, so the baseline is 3. The tool description does not add any additional meaning about parameters; it only mentions 'named IANA timezone' without explicitly linking it to the 'zone' parameter. This leaves the relationship between the description and the actual parameters unclear.
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 that the tool returns the current time for a specified IANA timezone, which is a specific and unambiguous purpose. It distinguishes itself from sibling tools like 'utc-time' by focusing on named timezones.
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 does not explicitly mention when to use this tool instead of alternatives such as 'utc-time'. The context is implied but not stated, so an agent may need to infer the appropriate use case from the name and description.
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.
Most tools have clearly distinct outputs: URL metadata, URL normalization, hostname labels, robots inspection, HTTP status catalog, time lookups, JSON validation, and hex encoding. The main ambiguity is between citation and normalize-url, which both return host/scheme information, and between timezone and utc-time, though the descriptions help clarify their different outputs.
All names use lowercase hyphenation, giving a surface-level consistency. However, the set mixes nouns like citation and timezone, verb-object forms like inspect-robots and normalize-url, and the unusual hex-ok, so there is no consistent naming pattern.
With 11 tools, the count is reasonable and within the well-scoped range. The tools span URL, time, and data utility categories without feeling redundant, though the breadth suggests a general-purpose utility server rather than a tightly focused one.
The set covers common URL, time, and simple data-validation needs, but the overall domain is broad and somewhat unclear. Obvious companion operations are missing, such as hex decoding, timezone conversion, or more detailed request inspection beyond the vague compatibility tool.