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?
The description states that the body is discarded, which implies no side effects. However, it does not disclose behavior for the other parameters (url, host, zone) or mention error handling, return values, or edge cases. With no annotations, this is insufficient.
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 exceptionally concise, using only two sentences. It is efficiently worded and front-loaded with the core purpose, though it omits necessary context.
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 lacks crucial context: no output schema is defined, the roles of extra parameters are unexplained, and there is no mention of expected behavior on success/failure. It is not complete enough for an agent to use confidently.
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 for url, host, json, and zone are present but do not clarify how they relate to the tool's purpose. The tool description adds no meaning to these parameters, leaving ambiguity about their roles in validating JSON.
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's purpose: to check if a body is valid JSON. It uses a specific verb ('check') and resource ('body'). It is distinguishable from sibling tools like normalize-url and utc-time.
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 scenarios where this tool would be preferred.
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: `timezone` and `tz-europe-london` both report current time, and `citation`, `normalize-url`, and `domain-shape` all inspect URL components. The mix of URL, HTTP, JSON, and clock tools makes it unclear which tool should be used for a given request.
Tool names mix noun phrases (`citation`, `status-catalog`), hyphenated action verbs (`normalize-url`, `validate-json`), and a specific timezone identifier (`tz-europe-london`). There is no consistent verb-noun or domain-based naming pattern across the set.
The server name suggests a clock/timezone tool, but 11 tools include many unrelated URL, HTTP, and JSON utilities. This is far more than needed for the apparent core purpose, and the extra tools add noise rather than value.
For the clock/timezone aspect, the set provides UTC time, named timezone lookup, and a list of IANA zones, which covers basic needs. However, the inclusion of unrelated URL/HTTP/JSON tools makes the completeness of the overall server muddled, and there is no timezone conversion or formatting utility.