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 carries the burden of behavioral disclosure, and it does state the primary behavior: returning the current time in a specified timezone. It does not disclose output format, invalid-zone handling, or default behavior, but for a simple read-only time lookup the core behavior is reasonably transparent.
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 an efficient one-line summary with no filler, front-loading the resource and scope. It is concise but leans toward a label rather than a full sentence, lacking a verb form or any parameter-oriented detail.
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?
Despite 100% schema coverage, the overall definition is incomplete for an agent: there is no output schema, no annotations, and the schema contains three apparently irrelevant parameters (url, host, json) with none required, yet the tool semantically needs a zone. The description does not clarify how the zone is supplied or what the response looks like.
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 the baseline is 3 and the description need not repeat parameter details. The description aligns with the 'zone' parameter but adds no extra meaning and does not help reconcile the unrelated url, host, and json parameters present in the schema.
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 returns the current time for a named IANA timezone, which identifies the core resource and scope. It is more informative than the tool name alone, but it does not name or contrast sibling tools such as utc-time or iana-zones.
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 phrase 'named IANA timezone' implies this tool is for getting timezone-specific current time, which is a reasonable usage context. However, it gives no explicit guidance on when not to use it or which alternative to choose, especially given the closely related utc-time and iana-zones siblings.
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 target distinct concerns such as URL normalization, robots parsing, timezone lookup, and JSON validation. A few URL/HTTP utilities overlap in input type, but descriptions clarify differences: citation adds HTTP status, normalize-url drops query/fragment, and domain-shape focuses on hostname labels.
Names consistently use lowercase hyphenation, but they mix noun-style names like status-catalog and timezone with verb-style names like inspect-robots and validate-json. There is no strong verb_noun pattern across the set.
11 tools is within a reasonable range for a mixed utility server covering URLs, HTTP, JSON, and time. A few entries like mime-json and compatibility feel marginal, but the overall count is not bloated.
The surface covers URL inspection, robots, HTTP status codes, JSON validation, and timezone utilities without obvious dead ends. Some related web utilities are absent, but the privacy-focused descriptions suggest those are intentionally excluded.