Common IANA timezone names for clock calls.
| 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 full burden of behavioral disclosure. It only states the content is 'common IANA timezone names' without saying whether the tool returns them, filters by zone, or ignores the url/host/json parameters. There is no mention of return shape, side effects, or failure behavior.
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 short but underspecified rather than concise; it omits the verb and actionable information while including only a vague 'for clock calls' hint. A one-sentence definition with a verb would fit the same length and be far more useful.
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?
With 4 optional parameters, no output schema, no annotations, and sibling tools present, the description is severely incomplete. An agent cannot determine what the tool returns, how parameters like url/host/json are used, or when to call it.
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 is 3. The description adds no semantic connection between the parameters and the tool's purpose—especially why url, host, and json appear in a timezone tool—but the schema already documents each parameter adequately.
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 is a noun phrase—'Common IANA timezone names for clock calls'—with no verb indicating what the tool does. It mostly restates the tool name (iana-zones) and adds a vague context hint, so it does not clearly distinguish the tool from siblings or state its action.
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 only usage signal is 'for clock calls,' which implies a context but does not explain when to choose this tool over alternatives like validate or normalize. No exclusions, prerequisites, or alternative tool guidance is provided.
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 a distinct shape or check, but `citation` and `normalize-url` both return URL host/scheme information, and `timezone`/`utc-time` overlap enough to cause occasional misselection. Overall, tool descriptions clarify the intended purpose in most cases.
All tool names are lowercase and hyphenated, which is a consistent casing convention. The mix of noun-style names like `citation` and verb-object names like `validate-json` is a minor semantic inconsistency but not a confusing one.
With 11 tools, the count is within a reasonable range for a lightweight utility server. Some reference-style helpers like `status-catalog` and `iana-zones` could be consolidated, but the set is not bloated.
The set covers URL, time, phone, JSON, and robots shape checks, but the broad 'shape' theme suggests notable gaps such as email or IP address shape validation and timezone conversion. These omissions are workable but could cause agent dead ends.