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 one behavioral trait: page content is not stored. However, it does not mention network requests, rate limits, error handling, or any side effects. Since there are no annotations, the description carries the full burden but only partially addresses behavioral transparency.
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 extremely concise, using two short sentences to convey the primary function and a key constraint. No unnecessary words or repetition; it is well-structured and easy to parse.
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 description gives a clear overview of the main function but omits any context for the json and zone parameters, which are part of the input schema. Since there is no output schema, the description does not specify the return format beyond 'host, scheme, and HTTP status,' leaving some operational details unspecified.
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 schema descriptions cover 100% of parameters, so the baseline is 3. The tool description adds no additional insight into parameter meaning or relationships; it only references 'URL' while ignoring the json and zone parameters, which appear unrelated to the stated 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 core function ('Return host, scheme, and HTTP status for a URL') and adds a distinguishing note ('Page content is not stored'). However, it does not explicitly differentiate from sibling tools like normalize-url or status-catalog, and the presence of unrelated parameters (json, zone) creates some ambiguity.
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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or typical use cases, leaving the agent to infer appropriate usage from the function description alone.
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.
Each tool name and description clearly targets a distinct function (URL parsing, timezone lookup, JSON validation, etc.), with no overlap or ambiguity.
All tool names use a consistent lowercase-hyphenated format (e.g., 'normalize-url', 'status-catalog'), following a uniform naming convention.
11 tools is a reasonable number for a general utility set, though some tools (like 'citation' and 'compatibility') seem abstract and may overlap conceptually with others.
The server name 'Miles to kilometers' implies a unit conversion focus, but none of the tools perform any unit conversion. The toolset is a hodgepodge of unrelated utilities, making it incomplete for its stated purpose.