Return host, scheme, and HTTP status for a URL. Page content is not stored.
| 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?
The only behavioral note is 'Page content is not stored.' This gives minimal insight into side effects, such as network requests, caching, or how the json and zone parameters are handled. Without annotations, the description carries the full burden and falls short.
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 very short and to the point, but its brevity contributes to ambiguity. It does not waste words, yet it fails to convey essential information about the tool's operation.
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 parameters and sibling tools, the description is incomplete. It does not explain how the parameters interact, what the output format is, or why certain parameters (json, zone) exist. An agent would likely struggle to invoke this tool correctly.
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?
Each parameter has a description, but they appear mismatched with the tool's stated purpose. For example, 'json' is described as 'JSON text to validate; discarded after the check' and 'zone' as 'IANA timezone name', which are not obviously related to returning host, scheme, or HTTP status. The descriptions add confusion rather than clarity.
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 states a clear verb and object ('Return host, scheme, and HTTP status for a URL'), but it is ambiguous how the provided parameters (url, host, json, zone) map to this purpose. It does not clearly differentiate from sibling tools like normalize-url or status-catalog.
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 given on when to use this tool versus alternatives. There is no mention of context, prerequisites, or edge cases that would help an agent choose this tool.
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 distinct purpose (country code, URL manipulation, timezone, JSON validation, etc.) with no overlapping functionality, so there is no ambiguity in selecting the right tool.
All names use lowercase with hyphens, but the pattern is inconsistent: some are noun-only (e.g., 'cc-jp', 'iana-zones') while others are verb-noun (e.g., 'normalize-url', 'validate-json'). The style is uniform but the grammar is mixed.
With 11 tools, the count is reasonable, but the collection feels like a random assortment of utilities rather than a focused feature set, making the size slightly unjustified.
There is no coherent domain to evaluate completeness against. The tools span unrelated areas (ISO, HTTP, timezones, JSON, robots), so the set is incomplete for any single purpose and lacks a clear scope.