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?
No annotations exist, so the description carries the full burden. It honestly discloses the read-only behavior of retrieving current time, but it does not state the output format, whether zone is the only operative input, or why url/host/json parameters appear in the schema.
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?
One short, front-loaded sentence with zero filler. Every word earns its place.
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 the statement is nearly sufficient, but it omits the return shape (ISO timestamp, offset, wall-clock) and leaves the three unrelated parameters unresolved. An agent cannot be fully confident about how to invoke it correctly.
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 the baseline applies. The description adds no meaning beyond the schema's existing 'IANA timezone name' for zone and provides no clarification on the relevance of url, host, and json to a timezone lookup.
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 states a specific verb+resource ('Current time' in a 'named IANA timezone'), making the tool's function immediately clear. None of the siblings (citation, compatibility, inspect, normalize, status, validate) suggests timezone time lookup, so it is fully distinguished without needing to open the schema.
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 gives no guidance on when to use this tool versus alternatives, nor any exclusions or context. An agent gets the basic function but no routing information.
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 distinct outputs, but there is real overlap: http-404 is a subset of status-catalog, timezone overlaps utc-time, and citation/normalize-url/domain-shape all parse URLs in slightly different ways. The descriptions clarify intended uses, so an agent can usually pick correctly, but the boundaries are not crisp.
Names are all lowercase kebab-case, which provides a surface-level consistency, but the structural pattern is mixed: single nouns, noun-noun compounds, and imperative verb-noun forms. This makes the naming scheme less predictable than a uniform verb_noun or noun-based convention.
Eleven tools is within a reasonable numeric range, but the set is not tightly scoped: URL/HTTP tools are mixed with timezone, JSON, and compatibility tools. A more focused HTTP utility server could easily justify fewer or more cohesive tools.
The inferred domain is URL/HTTP inspection, and the set covers normalization, status codes, and robots, but it lacks obvious related operations such as HTTP headers, redirects, or URL decoding. The presence of unrelated time and JSON tools makes the surface feel arbitrary rather than deliberately complete.