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, the description carries the burden; it discloses one meaningful trait ('Page content is not stored') that complements the schema's 'discarded after the check' for `json`. It doesn't say whether the tool makes live network requests or how failures/statuses are handled.
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 sentences contain the main action and a privacy note with zero waste; the key behavior is front-loaded.
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?
Only one of four parameters is meaningfully described, there is no output schema, no annotations, and no mention of why `json` and `zone` parameters exist — an agent cannot fully infer call patterns for those cases.
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 coverage is 100%, so the baseline is 3. The description adds return-value context for `url` (host/scheme/status) but adds nothing for `host`, `json`, or `zone`.
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?
States a specific action ('Return host, scheme, and HTTP status for a URL') but covers only the URL behavior while the schema accepts `json` and `zone` parameters. It doesn't differentiate from sibling `normalize-url` or explain the broader 'citation' bundle.
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 on when to use this tool versus siblings like `normalize-url` or `validate-json`, and no exclusions or prerequisites. The 'page content is not stored' remark weakly implies a lightweight check, but nothing explicit.
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 purpose, especially citation, normalize-url, and domain-shape, all of which inspect URLs or hostnames. The time-related tools utc-time and year-utc also overlap because a timestamp contains the year. Other tools are more distinct, but the boundary between these clusters is not always clear.
All names use lowercase kebab-case, which gives some visual consistency. However, the pattern is mixed: some are verb-object names (normalize-url, validate-json, inspect-robots), while others are standalone nouns or noun-noun compounds (citation, timezone, status-catalog, year-utc). This makes the naming readable but not predictably consistent.
Eleven tools is a reasonable number for a utility-style server, neither too sparse nor overwhelming. The count feels slightly inflated by the mixed domains, but no individual tool is redundant enough to cut. Overall, the count is appropriate for a general-purpose utilities server.
The set covers a few small domains—URL inspection, time/timezone, HTTP status, and JSON validation—but none are fully fleshed out. For example, there is no timezone conversion or date formatting tool, and URL tools lack any operation for actual page retrieval. While the tools are self-contained, the overall surface feels more like a collection of samples than a complete workflow.