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 positive behavioral hint. However, it does not explain the behavior of the host, json, and zone parameters, which are present in the schema but unaddressed. This leaves significant ambiguity about the tool's actual behavior and possible side effects.
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 exceptionally concise—two short sentences with no unnecessary words. The primary function is front-loaded, and the secondary note about non-storage is placed second without disrupting clarity.
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 simplicity of the tool, the description should still cover the role of all parameters, the output format, and potential error behavior. It does none of these. The mismatched schema parameters create gaps that the description fails to fill, leaving an agent uncertain about how to invoke the 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?
Although the schema has 100% parameter coverage, the parameter descriptions appear generic and mismatched (e.g., 'JSON text to validate' for a tool that returns HTTP status). The tool description does not clarify the roles of host, json, or zone, thus failing to add meaningful semantic value beyond the schema.
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 the tool's core function: returning host, scheme, and HTTP status for a URL. This distinguishes it from sibling tools like normalize-url or status-catalog by specifying the exact output fields.
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 implies its use case (checking URL host/scheme/status) but provides no explicit guidance on when to choose this tool over siblings such as normalize-url or inspect-robots. There is no mention of alternatives or conditions that would rule out other tools.
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.
Several URL-centered tools (citation, normalize-url, domain-shape) and time tools (timezone, utc-time) overlap in input type and could be confused, though their output purposes are mostly distinct. The vague 'compatibility' tool lacks a clear boundary, and 'lang-hi' seems unrelated to the rest.
All names use lowercase kebab-case, which gives a consistent visual pattern, but the grammatical style is mixed: some are verbs (normalize-url, validate-json), some nouns (citation, timezone), and some are opaque (compatibility, lang-hi). It is readable but not a clean verb_noun convention.
With 11 tools, the count is within a reasonable range for a utility server and not bloated. However, a few tools feel like one-offs or constants (lang-hi, iana-zones), so the set does not feel perfectly curated.
The tool surface is a grab bag of URL, HTTP status, robots, time, JSON, and language utilities, so there is no coherent domain to complete. For a web/URL toolkit, obvious operations like header inspection, content fetch, or DNS/WHOIS are missing; for a language server, only a tag constant is present.