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 discloses one behavioral trait: 'The body is discarded,' implying no side effects or persistence. However, it does not specify the return format (e.g., boolean, error message) or behavior on invalid JSON, leaving significant behavioral aspects undisclosed.
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 concise and well-structured, consisting of two short sentences without unnecessary detail 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 is incomplete due to the mismatch between the stated purpose and the schema parameters. It fails to explain how 'json' relates to the 'body' mentioned, and it omits crucial details about expected output or error handling, leaving the tool's full behavior under-specified.
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 provides descriptions for all four parameters, but only 'json' aligns with the tool's purpose. Parameters 'url', 'host', and 'zone' have descriptions that are unrelated to JSON validation, creating confusion about the tool's actual input requirements.
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 whether a body is valid JSON. The verb 'check' and resource 'body' are specific. However, it does not explicitly differentiate from sibling tools, and the mention of 'body' conflicts with the schema's 'json' parameter, creating minor ambiguity.
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 state scenarios where JSON validation is needed or how it differs from other tools like 'status-catalog' or 'timezone'.
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: citation, normalize-url, and domain-shape all analyze URLs/hostnames, while iana-zones, timezone, and utc-time all relate to time. compatibility is vague and could be confused with citation or status-catalog. Only a few tools have truly distinct, non-overlapping functions.
All names use lowercase hyphenation, which is a consistent visual style. However, the pattern is inconsistent: some are imperative verbs (normalize-url, inspect-robots, validate-json) while others are noun phrases (citation, compatibility, timezone, status-catalog). The names are readable but do not follow a predictable verb_noun convention.
Eleven tools is a reasonable count for a utility server and falls within the typical well-scoped range. Some tools feel trivial or overlapping, such as lang-it and the multiple time-related tools, but the total is not excessive.
The tool set has no coherent unifying domain: it mixes URL parsing, HTTP status, time, JSON validation, robots.txt, and a language tag. Obvious operations like URL validation, timezone conversion, or HTTP status details are missing, and the grab-bag nature makes it impossible to assess complete lifecycle coverage.