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?
No annotations are provided, and the description gives no information about side effects, permissions, or whether the tool reads or writes. The tool's behavior is completely undisclosed.
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 fluff, but it is far too brief for a tool with four parameters and a complex purpose. It lacks the substance needed to be appropriately sized.
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 tool's apparent purpose, the description is severely incomplete. It does not explain the function, the relationship between parameters, or any return behavior, leaving the agent without essential 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 parameter descriptions are shallow and unrelated to the stated purpose. The tool is about timezone names, yet the schema includes url, host, and json, which have no apparent connection, making the parameters confusing and not semantically meaningful.
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, not an action, and does not state what the tool actually does. It mentions 'Common IANA timezone names' but gives no verb or clear function, leaving the tool's purpose ambiguous.
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 on when to use this tool versus the sibling tools like timezone or utc-time. The description fails to provide any context or selection criteria.
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 clearly distinct purposes, but there is some overlap between URL-related tools (citation vs normalize-url) and time-related tools (timezone vs utc-time). Overall, the descriptions are clear enough to avoid major confusion.
The naming is inconsistent: some tools are nouns (citation, timezone, status-catalog), some are verb phrases (inspect-robots, normalize-url, validate-json), and one is an abbreviated pair (lang-fr). The hyphenated style is consistent, but the verb/noun mix makes the set feel incoherent.
With 11 tools, the count is within a reasonable range and each tool adds a distinct capability. It is not overly large, though some tools feel like a grab-bag of unrelated utilities.
The tools cover a variety of network, time, and data-validation utilities, but the scope is unclear. Given the server name 'Language fr', there is very little language-specific functionality beyond lang-fr, so the completeness relative to the implied domain is limited.