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 are provided, and the description does not disclose behavior such as whether only the zone parameter is meaningful, what happens to the other accepted parameters, or how the current time is formatted. The extremely brief description leaves important behavioral context unstated.
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 single sentence is appropriately concise and front-loaded, containing no fluff. However, it is so brief that it omits potentially useful context without becoming bloated.
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?
Given no annotations and no output schema, the description alone is insufficient. It does not describe the return value, clarify the role of the unrelated parameters, or mention any edge cases or limitations of the timezone lookup.
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. The description adds little beyond the schema's zone parameter description, and it does not clarify why url, host, and json appear in the schema or whether they are ignored.
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 conveys that the tool returns the current time for a specified IANA timezone, which distinguishes it from siblings like citation or normalize. It lacks an explicit verb but the purpose 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?
There is no guidance about when to use this tool versus alternatives, and no mention of how it relates to sibling tools. The description implies use for timezone lookups but gives no exclusions or 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.
Several tools overlap in the URL/host space (citation, normalize-url, domain-shape, inspect-robots), so an agent may need to read descriptions carefully to select the right one. The time and HTTP tools are mostly distinct, but 'compatibility' is vague enough to create selection uncertainty.
All names use lowercase kebab-case, but the underlying convention is mixed: verb-first names like normalize-url and validate-json coexist with noun-first compounds like semver-parse and domain-shape, plus bare nouns like citation and timezone. The set is readable but lacks a consistent naming pattern.
For the broad set of read-only utilities exposed, 11 tools is a reasonable count and none feels redundant. However, the scope spans URLs, time, HTTP status, JSON, and semver, which feels slightly broad for a server whose name implies a narrow 'SemVer numbers only' purpose.
The tools cover several useful read-only operations, including URL inspection, time lookups, status codes, JSON validation, and semver parsing. The overall domain is diffuse, and there are notable gaps such as timezone conversion, URL redirect/validation details, and semver comparison.