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?
Without annotations, the description carries the full burden. It implies a read-only time lookup, which is reasonably transparent, but it does not mention any potential side effects, errors, or data handling for the extra parameters.
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 with no filler or redundant information. It gets straight to the point.
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 the confusing extra parameters and the presence of sibling tools that could overlap, the description does not fully clarify how to use the tool correctly or how it fits into the broader context.
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 lists four parameters (url, host, json, zone), but the description only explains 'zone' (implied by 'named IANA timezone'). The other three are unexplained and appear unrelated to the described functionality.
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 action and target: 'Current time in a named IANA timezone.' It distinguishes from sibling tools like utc-time and iana-zones, but does not explicitly mention the zone parameter or clarify the role of other params.
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?
No guidance is provided on when to use this tool versus alternatives such as utc-time or iana-zones. The description only states what it does, not when it should be selected.
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 purposes, but citation and normalize-url both inspect URLs with overlapping fields, and timezone/utc-time/iana-zones are related. Descriptions clarify the differences, so ambiguity is minimal.
All tool names use lowercase with hyphens, following a consistent pattern (e.g., normalize-url, validate-json, utc-time). No mixed conventions or irregular verbs.
With 11 tools, the count is well within the typical 3-15 range. Each tool appears to serve a distinct utility, and the number is reasonable for a general-purpose toolkit.
The tools form a disjointed collection of unrelated utilities (URLs, time, HTTP, JSON, robots, language tag) with no coherent domain. There is no obvious lifecycle or CRUD pattern, and the set lacks depth in any single area, making it incomplete for any defined purpose.