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?
No annotations are present, so the description carries the full behavioral disclosure burden. It adds the useful privacy note 'Page content is not stored,' but it does not disclose whether a network request is made, side effects, failure modes, or the behavior associated with the json and zone parameters.
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 two sentences are concise and the privacy note earns its place. The description is front-loaded with the primary function, though it omits important mode context.
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?
For a four-parameter tool with no output schema and no annotations, this description is incomplete. It explains only the URL path and omits JSON-validation and timezone behaviors, return structure for those modes, and error/edge-case handling.
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. The description adds no meaning for json or zone and its URL-only framing could mislead, but it does not contradict the schema's per-parameter descriptions.
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 concrete outcome—'Return host, scheme, and HTTP status for a URL'—so it is not a tautology. However, the input schema includes json and zone parameters that the description never mentions, and it does not differentiate this tool from siblings like normalize-url or validate-json.
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 gives no guidance on when to use citation versus siblings such as normalize-url, status-catalog, validate-json, or timezone. There are no conditions, exclusions, or alternative-selection cues.
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 distinct, but there is overlap in the URL/time clusters: citation, normalize-url, and domain-shape all involve host/scheme data, while timezone and utc-time both return current time. The vague compatibility tool also adds ambiguity.
Names mix noun-only forms (citation, timezone), verb-object forms (inspect-robots, normalize-url, validate-json), and compound nouns (iana-zones, status-catalog, utc-time). There is no consistent naming convention across the set.
Ten tools is a reasonable count for a general-purpose utility server. Each tool is lightweight and the set is neither bloated nor too sparse.
The domain is an open-ended 'utility index,' so completeness is hard to define; it covers URL handling, time, HTTP status, robots, and JSON validation. However, obvious common utilities like hashing, encoding, or string operations are absent, leaving notable gaps for a general utility server.