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 provided, so the description carries the full burden. It discloses a meaningful behavioral fact ('Page content is not stored'), signaling a privacy-conscious fetch operation. However, it doesn't mention whether an HTTP request is made, redirect handling, rate limits, or auth requirements.
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 zero filler. The core purpose is front-loaded, and the privacy caveat is added as a secondary sentence. Every word earns its place.
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 accepts four unrelated parameters, has no output schema, and no annotations. The description only explains the URL aspect and not the json/zone/host parameters' roles or expected outputs. For a tool this overloaded, the description is incomplete.
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 each parameter is already documented in the input schema. The description only covers the 'url'-related behavior and adds no meaning for the 'host', 'json', and 'zone' parameters, but the baseline 3 applies since the schema does the heavy lifting.
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 a specific action and resource: 'Return host, scheme, and HTTP status for a URL.' This is informative and matches the primary purpose, though it doesn't explicitly differentiate from sibling tools since none are provided.
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 use this tool versus alternatives, or when not to use it. The description only explains what the action returns, leaving the agent to infer appropriate usage.
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.
Timezone, tz-asia-tokyo, and utc-time all return current time with overlapping purposes, and compatibility is vague about what it classifies. The mix of time and URL tools under a clock server name further confuses selection.
Tool names are mostly lowercase with hyphens, but the pattern mixes nouns (citation, timezone), verbs (inspect-robots, normalize-url), and a special abbreviation (tz-asia-tokyo). The style is readable but not uniformly verb_noun.
11 tools is within the typical well-scoped range, but the server's apparent focus is unclear — half are time-related and half are URL/HTTP utilities. The count is not excessive, though the breadth feels unaligned with the server name.
The time domain covers current time, UTC, and timezone names, but lacks timezone conversion or date formatting. The URL utilities are a partial set with no page fetch, headers, or query handling, leaving notable gaps for a general web tool surface.