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?
With no annotations, the description carries the disclosure burden. It usefully states that the body is discarded, signaling no persistence, but it does not say what the tool returns, whether the check has side effects, or whether it is local or remote.
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 with no filler. The core purpose is front-loaded, and the second sentence adds a genuinely useful behavioral note without bloating the definition.
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?
For a 4-parameter tool with no output schema and no annotations, this is too thin. It does not identify json as the parameter to pass, explain the return value, or clarify why url, host, and zone exist in the schema. An agent is likely to be confused by the unrelated parameters.
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 schema coverage is 100%, the parameter descriptions are at odds with the tool's purpose: url, host, and zone are clearly unrelated to validate-json. Only json is relevant, and its description mostly restates the tool description. The description never tells the agent to ignore the unrelated fields.
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 specific action ('check whether') on a clear resource ('a body is valid JSON'), which is reinforced by the tool name. It does not contrast with sibling tools, so it misses the distinguishability bar for a 5.
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 intended use is implied by 'Check whether a body is valid JSON' — an agent can infer when to use it. However, there is no guidance on when not to use it or which sibling tools might be alternatives.
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 URL-focused tools (citation, normalize-url, domain-shape) overlap in what they inspect, though their descriptions do specify different outputs. compatibility and sha256-ok are vague, but most other tools have clearly separate jobs.
All names use lowercase hyphenation, but they mix verb-object names (normalize-url, inspect-robots, validate-json) with noun-only or noun-noun names (citation, timezone, status-catalog, iana-zones). This is readable but gives agents no reliable pattern for predicting tool names.
Eleven tools is within a reasonable size for a general-purpose privacy-safe utility server, and no tool is an exact duplicate. The set could be tightened around a single domain, but the count itself is not excessive.
The server's domain is too broad and unfocused to define a complete workflow: URL inspection lacks redirect/header coverage, timezone handling lacks conversions, and JSON/hash tools are single-purpose checks. As a result, agents will likely need tools outside this server for related operations.