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?
With no annotations present, the description carries the behavioral disclosure burden. It does add a meaningful non-storage guarantee: 'Page content is not stored.' However, it does not disclose whether the tool makes network requests, how failures are handled, or any other side-effect profile, leaving notable gaps.
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 two short sentences with no redundancy. The primary result is front-loaded, and the additional privacy-relevant note about not storing page content earns its place. This is appropriately concise and 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 tool has four parameters and no output schema, yet the description only addresses URL-citation behavior. The presence of json and zone parameters, alongside siblings like validate-json and timezone, suggests additional modes or behaviors that the description omits. An agent could not confidently determine what happens when those parameters are supplied.
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 and the description need not repeat parameter meanings. The phrase 'for a URL' weakly maps to the url parameter, but the description adds no semantic context for host, json, or zone beyond what the schema already provides.
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 specific action and resource: 'Return host, scheme, and HTTP status for a URL.' This is clear at the sentence level and implies a distinction from siblings like normalize-url. However, the description does not mention or reconcile the additional schema parameters (host, json, zone), so the overall tool purpose is only partially 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?
There is no explicit guidance on when to use this tool versus alternatives such as normalize-url, status-catalog, validate-json, or timezone. The description implies URL-related use, but it never states exclusions, prerequisites, or a decision rule for selecting this tool over nearby siblings.
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 in the URL/host/status space: citation, normalize-url, and domain-shape all return host-like information, and compatibility is vague. The descriptions help separate them, but an agent could still misselect when looking for a specific URL metric.
Names mix single-word nouns like citation and timezone, noun phrases like domain-shape and status-catalog, and verb-led names like normalize-url and validate-json. All use kebab-case, but there is no consistent verb/noun pattern across the set.
Eleven tools is within a reasonable range for a utility server. Most tools have narrow, distinct purposes, though a few time-related and URL-related tools feel somewhat redundant.
The set covers URL normalization, JSON/JWT inspection, robots, HTTP status, and time utilities, but the lack of a single cohesive domain leaves noticeable gaps. For example, there is no generic URL validation, no HTTP header inspection, and the compatibility tool is underspecified.