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?
There are no annotations, so the description carries the full burden of behavioral disclosure. It does add a meaningful privacy behavior: 'Page content is not stored.' However, it does not disclose whether a network request is made, how redirects or errors are handled, or what exactly the return object contains beyond the three named fields.
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?
Two short sentences, both informative: the first states the primary behavior and the second adds a privacy clarification. There is no filler or unnecessary repetition.
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 four parameters, zero annotations, no output schema, and a large set of related sibling tools, the description is too narrow. It covers only the URL case and omits the purpose and use of the `json` and `zone` parameters, leaving the tool materially incomplete from an agent's perspective.
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?
Schema description coverage is 100%, so the baseline is 3 even without extra parameter detail in the tool description. The description adds little beyond the schema for `url` and does not explain how `host`, `json`, and `zone` relate to the declared URL-citation behavior, leaving their role ambiguous.
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 action ('Return host, scheme, and HTTP status for a URL') and adds a useful privacy qualifier. It is reasonably distinct from sibling tools like normalize-url and status-catalog, though it does not explicitly name alternatives. The main ambiguity is that the schema also includes `host`, `json`, and `zone` parameters, which the description does not address.
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 about when to prefer this tool over the many overlapping siblings such as normalize-url, status-catalog, inspect-robots, or validate-json. The description implies URL-checking usage but does not state what it is not for, when it should be avoided, or which alternatives exist.
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 tools overlap: citation and normalize-url both return URL origin/host information, while timezone and utc-time both provide current time. The descriptions help separate most tools, but compatibility is vague and could be confused with classification or request-checking tools.
Names use lowercase hyphenation and are generally readable, but they mix verb-led forms like inspect-robots, normalize-url, and validate-json with noun-led forms like domain-shape, status-catalog, and utc-time. There is no consistent verb_noun or noun_verb convention across the set.
11 tools is a reasonable count, but for a server named 'Nano ID shape check' the scope feels diffuse, with URL, time, JSON, and HTTP status utilities included. Several tools do not clearly earn their place under that stated purpose.
The server claims a narrow Nano ID focus, yet only one tool directly supports it, while URL, JSON, time, and robots checks are shallow one-offs. There are no tools for generating or custom-validating Nano IDs, and URL handling stops at normalization without redirects or deeper request inspection.