Check whether a body is valid JSON. The body is discarded.
| 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 present, so the description must fully disclose behavior. It notes the body is discarded, but it does not state whether the operation is read-only, what the return value is, or how errors are handled. Minimal disclosure leaves significant gaps.
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 a single, concise sentence with no fluff. However, it is so brief that it sacrifices necessary context, making it more under-specified than appropriately concise.
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?
With four parameters and no output schema, the description is insufficient. The unrelated parameters (url, host, zone) suggest a possible mismatch between description and schema, leaving an agent unsure how to use the tool correctly.
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?
While the schema provides descriptions for all parameters (100% coverage), the tool description does not clarify that the 'json' parameter is the 'body' being validated. It also ignores the other parameters (url, host, zone), which appear irrelevant to JSON validation, creating confusion about their 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 states a clear action (check validity) and resource (JSON body), distinguishing it from sibling tools like normalize-url or timezone. However, 'body' is ambiguous—the schema includes a 'json' parameter but also unrelated fields (url, host, zone), so it's not explicit which parameter is validated.
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 provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or when to choose this over other validation or URL/timezone tools.
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 clear, distinct purposes (e.g., timezone vs. normalize-url). The only minor overlap is between 'timezone' and 'tz-europe-madrid', but they differ in generality (any named zone vs. a fixed zone).
All tool names follow the same lowercase, hyphen-separated pattern (e.g., 'tz-europe-madrid', 'utc-time', 'validate-json'). No mixed conventions or inconsistent verb usage.
11 tools is a reasonable number. The set includes several non-clock utilities (URL, JSON, robots) that broaden scope beyond the server's name, but the count itself is not excessive or too sparse.
For a clock/time server, core operations are covered: UTC time, named timezone, and a specific fixed zone. The 'iana-zones' tool aids discovery, though a full zone list or conversion functionality is missing. Extra web/JSON tools are unrelated but not a defect.