Check whether text 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 provided, so the description must carry the burden of behavioral disclosure. It does reveal that the input body is discarded, which is useful, but it never states what the tool returns, how invalid JSON is signaled, or whether any other side effects occur.
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: two short sentences, with the primary purpose front-loaded. Every word earns its place, and there is no redundant filler.
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 tool is simple, but with no output schema and no annotations, the description leaves critical gaps. An agent cannot tell whether the tool returns a boolean, throws on invalid JSON, or which parameters are actually used, making the description incomplete for confident invocation.
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?
Schema coverage is 100%, so the baseline is 3. The schema adequately describes the 'json' parameter, but the description itself adds no parameter-level guidance. It also fails to clarify that the other three schema parameters, 'url', 'host', and 'zone', appear irrelevant to this tool, potentially confusing an agent.
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 text is valid JSON', which clearly identifies the tool's function and distinguishes it from all listed siblings. The additional note about the body being discarded reinforces the focused scope.
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 clearly implies its use case: when an agent needs to determine whether a given text is valid JSON. It does not explicitly name alternatives or exclusions, but none of the sibling tools overlap with this functionality, so the context is sufficient.
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.
citation, normalize-url, and domain-shape all dissect URLs/hostnames, and status-catalog overlaps with citation's HTTP status reporting. compatibility is too vague to disambiguate, so an agent could easily pick the wrong URL-analysis tool.
All names are lowercase and hyphen-separated, which is readable, but the pattern is mixed: inspect-robots, normalize-url, and validate-json use verb-noun while citation, domain-shape, and status-catalog are nouns. This is inconsistent but not chaotic.
Ten tools is not inherently too many, but for a server named 'JSON Check' only validate-json is on-topic. The remaining nine are unrelated URL, HTTP, and time utilities, making the toolset feel like a grab bag rather than a scoped set.
As a JSON-checking server it is severely incomplete: only a boolean validity check is offered, with no schema validation, formatting, or JSON-path operations. As a general URL/HTTP utility it also lacks HTTP body access, redirect handling, and timezone conversion, so common workflows will hit dead ends.