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, the description must carry the behavioral burden. It conveys a read-only, current-time behavior and names the input domain, but it does not disclose output format, invalid-timezone handling, or why unrelated fields like url/host/json appear in the schema. No contradiction exists, but the transparency is minimal.
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 sentence with no filler, and the core action is front-loaded. Every word contributes to understanding the tool.
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 tool with no output schema and four optional parameters, one line is not enough. The description does not explain how the time is returned, whether zone is effectively required, or what roles the other schema fields play, leaving meaningful ambiguity for invocation.
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 description coverage is 100%, so each parameter is already documented at the schema level. The description does not add guidance about zone being the operative parameter or clarify the purpose of url, host, and json, but the high coverage keeps this dimension at baseline.
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 identifies the resource (a named IANA timezone) and the behavior (getting the current time), and it is topically distinct from sibling tools like citation or validate-json. It lacks an explicit verb such as 'get' or 'return', but the intended action is unambiguous.
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 intended usage is implied: an agent needing the current time for a timezone should select this tool. However, the description gives no explicit guidance about when not to use it or whether alternatives exist, so the usage context is only implicitly conveyed.
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.
Several tools are distinct, but citation and normalize-url both return URL-derived fields, and timezone/utc-time overlap in purpose. compatibility is vague enough that an agent could struggle to know when to use it over the URL inspection tools.
Names mix bare nouns (citation, timezone, compatibility) with verb-noun forms (inspect-robots, normalize-url, validate-json). The hyphenated style is consistent, but the grammatical pattern is not, making the set feel ad hoc.
Ten tools is not inherently too many, but the set includes unrelated areas like timezones, HTTP status codes, and JSON validation under a URL Normalize server. Several tools do not clearly earn their place relative to the stated purpose.
The only tool directly addressing the server's core purpose is normalize-url, and it only returns origin, host, and path. Missing URL comparison, query/fragment handling, or rewrite capabilities leaves the main workflow incomplete, while unrelated tools do not fill those gaps.