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?
The description discloses that page content is not stored, which is a meaningful behavioral trait beyond the basic return value. It also implicitly indicates no content retrieval, but does not elaborate on potential side effects like network calls or error handling.
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 concise, two sentences, and front-loaded with the core action. It efficiently communicates the main functionality and a key constraint without unnecessary detail.
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 simple tool, the description covers the primary behavior and a privacy aspect. However, it omits any information about return format, error cases, or how the extra schema parameters relate to the task. The presence of mismatched schema fields reduces completeness, as the description does not resolve the confusion.
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?
The description gives partial meaning for the 'url' parameter by stating it is a URL to return host, scheme, and status for. However, it does not clarify the remaining parameters (host, json, zone) that appear in the schema, leaving their relevance or usage ambiguous. The schema descriptions are generic and not reconciled with the tool's purpose.
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 the tool returns host, scheme, and HTTP status for a URL, which is a specific verb and resource. It also mentions a key non-goal (not storing page content), making the purpose unambiguous even without sibling comparison.
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 lacks explicit guidance on when to use this tool versus alternatives like normalize-url or status-catalog. It does not mention any prerequisites or conditions for selection, leaving the agent to infer usage context from the tool name and sibling list.
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.
Some tools have overlapping concerns: citation and normalize-url both parse URLs and return host/scheme, and timezone and utc-time both provide current time. compatibility is also vague, making its relationship to the other tools unclear.
Names are consistently lowercase with hyphen separators and mostly use noun phrases, with a few verb phrases (inspect-robots, normalize-url, validate-json). The pattern is readable but not perfectly uniform.
Eleven tools is within the typical well-scoped range, though the set covers a broad mix of URL, HTTP, time, and JSON utilities rather than a single focused domain.
The set covers common inspection tasks (URLs, robots.txt, HTTP status, timezones, JSON validity), but it lacks deeper operations like URL content retrieval, ISO duration conversion/parsing beyond shape, or more comprehensive HTTP status/request details.