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 disclosure burden. It adds one useful behavioral fact—'Page content is not stored'—which covers data retention, but it does not disclose fetching side effects, redirect handling, or output shape.
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; the key output is front-loaded in the first sentence and the privacy note earns its place in the second. There is no filler.
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?
Despite schema coverage, the description omits how host, json, and zone relate to the URL/status output, and there is no output schema or annotation context. An agent cannot tell whether the json/zone parameters are independent modes or part of a citation check, so the tool is incompletely specified for invocation.
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 already describes all four properties with 100% coverage, so the description does not need to repeat them. It adds no parameter-level detail beyond the schema, so the baseline 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 first sentence is a specific verb+resource statement: it returns host, scheme, and HTTP status for a URL. This clearly conveys the core function, but it does not explicitly distinguish the tool from siblings such as normalize-url or status-catalog.
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 gives no guidance on when to prefer citation over normalize-url, status-catalog, validate-json, or timezone. It only states what it returns, not the scenarios or exclusions.
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.
Most tools have distinct outputs, but citation and normalize-url both return URL components and overlap on host/scheme. The time-related tools (iana-zones, timezone, utc-time) share a domain, and compatibility is vague enough that an agent may struggle to select it correctly.
All names are lowercase and kebab-case, which gives a consistent visual style. However, the naming mixes noun labels like citation and timezone with verb phrases like inspect-robots and validate-json, so there is no uniform verb_noun pattern.
Eleven tools is a reasonable count, but the server is named 'UUID Mint' and contains a loose collection of URL, time, HTTP, JSON, and UUID utilities. The count is not excessive, but the tools do not form a cohesive, well-scoped set.
The tool surface is a grab bag with no coherent domain, so common workflows are only partially covered. For example, there is UUID generation but no UUID validation, timezone lookup but no timezone conversion, and URL inspection but no full URL parsing or content retrieval.