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 description discloses that page content is not stored, which is a useful side-effect note. However, it does not clarify how the extra parameters (host, json, zone) are handled or whether the tool makes an HTTP request. Behavior around these inputs remains opaque.
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 concise and front-loaded, using two sentences to convey the main purpose. It could be slightly more detailed without becoming verbose, but overall it is well-structured.
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?
The description is incomplete given the complexity of the schema. It does not explain the purpose of the additional parameters (host, json, zone), leaving gaps in understanding what the tool actually does beyond returning URL metadata.
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 short descriptions for each parameter, but they do not align with the tool's stated purpose. For example, 'json' is described as validation text, but validation is not mentioned in the main description. The semantics of the parameters are poorly integrated with the tool's core function.
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 a specific action (return host, scheme, and HTTP status) for a URL, and notes that page content is not stored. However, the input schema includes parameters like json and zone that are not mentioned in the description, creating ambiguity about the tool's full purpose.
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 description does not explicitly state when to use this tool versus alternatives such as normalize-url or status-catalog. It implies usage when host/scheme/status are needed, but no clear guidance or exclusions are 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 are clearly distinct, but 'citation' and 'compatibility' have vague descriptions that could overlap with HTTP status handling, and 'status-catalog' adds further potential confusion. URL-related tools are distinguishable but require careful reading.
All names consistently use lowercase hyphenated style, but they mix noun phrases like 'timezone' and 'status-catalog' with verb-object forms like 'normalize-url' and 'validate-json'. This is mostly predictable but not perfectly uniform.
With 11 tools, the set is reasonably sized and not overwhelming. Each tool appears to serve a single utility purpose, fitting the apparent web-utility domain.
The collection covers common web development utilities: URL handling, HTTP status, time, timezone, JSON validation, robots.txt inspection, and language tags. There are no major dead ends, though the server name 'Language zh' does not strongly align with the broader tool set.