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 provided, the description carries the full burden and adds one useful disclosure: 'Page content is not stored.' However, it omits the tool's other behaviors implied by the schema — JSON validation and timezone checks — and says nothing about network fetching, failure modes, or 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?
Two short sentences with the main function front-loaded and the privacy-related constraint placed second. Nothing is wasted, though the description could better earn its place by covering the JSON and timezone capabilities.
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 4 heterogeneous optional parameters with no output schema and no annotations, yet the description only addresses URL citation. An agent would be blindsided by json and zone parameters, and there is no mention of what happens when these 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 schema already documents all four parameters. The tool description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.
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 verb and resource: 'Return host, scheme, and HTTP status for a URL.' This is clear and actionable. It does not explicitly differentiate from siblings like normalize-url or status-catalog, but the core function is unambiguous.
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 on when to use this tool versus alternatives. The description never mentions normalize-url, status-catalog, or any other sibling, and there is no exclusion criteria or recommended context.
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 fall into overlapping clusters: citation and normalize-url both process URLs, while timezone, utc-time, and unix-now all report current time. The descriptions clarify the exact output of each, but an agent could still struggle to pick between them without careful reading.
All names are lowercase and hyphenated, giving a consistent visual style. However, the pattern mixes noun phrases (citation, status-catalog, unix-now) with verb-noun imperatives (inspect-robots, normalize-url, validate-json), so there is no single predictable naming convention.
Eleven tools is within the typical well-scoped range and each utility has a narrow function. The count itself is reasonable, although the server name suggests a time-focused purpose while many tools are actually web/URL utilities.
The set covers common stateless operations: current time, timezone lookups, URL inspection, robots, and JSON validation. Notable gaps include epoch-to-human timestamp conversion and a way to fetch or inspect HTTP response details beyond status, which would be expected in a general utility server.