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 explicitly notes that the body is discarded, which is a relevant side effect. However, it does not explain other behavioral aspects like return format or error handling, and the parameter descriptions are misleading, which detracts from overall 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 and to the point, using only two short sentences. There is no unnecessary verbosity or redundancy.
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 essential context such as what constitutes a 'body', how the tool should be called, and why unrelated parameters exist. The mismatch between the tool's purpose and its parameters means the description is incomplete for reliable use.
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?
Although every parameter has a description, most are irrelevant to JSON validation: 'url' is described as an HTTPS URL to normalize, 'host' as a public hostname, and 'zone' as an IANA timezone name. Only 'json' has a relevant description, so the parameter semantics are actively misleading.
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 function: checking whether a body is valid JSON. However, the parameter list includes unrelated fields (url, host, zone) that contradict the stated purpose, so it is not perfectly clear.
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 selection criteria or context, leaving the agent without direction for appropriate invocation.
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 are clearly separate: URL parsing, robots inspection, time lookups, and JSON validation occupy distinct niches. The main confusions are citation vs normaliz-url, both URL inspection, and compatibility, whose classification purpose is vague.
All names use kebab-case, but the parts of speech vary: normalize-url and validate-json are verb-object, while citation, timezone, and iana-zones are noun phrases. This makes the naming readable but not a consistent pattern.
At 11 tools, the server is within the well-scoped range and no tool feels redundant. The scope is broad—URLs, HTTP, time, JSON—but the count itself is not excessive.
As a loose utility server, it offers a few operations per category rather than full coverage: time has current/lookup but no conversion, URL has inspection but no content fetch by design. Missing obvious helpers like URL comparison or timezone conversion, though the server likely aims to be minimal.