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 and no description of side effects, read-only behavior, network access, or output behavior, the description carries the full transparency burden and does not disclose any behavioral traits.
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 redundant words, though its brevity contributes to incompleteness rather than inefficiency.
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 lack of annotations, output schema, and usage guidance, the description is far from complete enough for an agent to reliably know what the tool returns, how to invoke it, or when to select 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?
The schema provides descriptions for all four parameters, but the tool description does not clarify how url, host, and json relate to iana-zones, leaving the parameter roles ambiguous and potentially misleading.
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 conveys that the tool relates to common IANA timezone names for clock calls, but it lacks an explicit verb such as 'list' or 'get', making the exact operation inferable rather than stated.
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 about when to use this tool instead of sibling tools like timezone or utc-time, nor is there any indication of appropriate scenarios or exclusions.
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.
Each tool has a clearly distinct purpose, covering URL analysis, time/date, HTTP status, robots.txt, and JSON validation with no significant overlap or ambiguity.
All tool names use a consistent lowercase-with-hyphens convention, matching the style across the entire set with no mixed casing or underscores.
The set of 11 tools is reasonable for a general-purpose utility server, providing a moderate breadth without feeling bloated or sparse.
The domain appears to be 'web developer utilities,' and while it covers common needs like URL handling, time, HTTP status, and JSON, some expected utilities (e.g., base64, HTML escaping) are missing, making it slightly incomplete.