ZapifyAPI MCP Server

validate_json

Validate JSON strings for correctness and format them with customizable indentation for clearer readability.

Instructions

Validate and format a JSON string.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "json": "<json>"
    },
    "name": "validate_json"
  }
}

Input Schema

Name	Required	Description	Default
`json`	Yes	JSON string to validate
`indent`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action without revealing how errors are handled, what 'format' outputs (e.g., indentation, minification), or any side effects. The presence of an `indent` parameter is not mentioned, so the tool's behavior regarding formatting remains opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no wasted words, making it concise and front-loaded. However, it is so brief that it omits critical details, so while structure is good, the content could be more descriptive without hurting conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with two parameters and no output schema or annotations, the description should at least clarify what 'format' does, mention the `indent` parameter, and describe behavior for invalid JSON. The current text leaves these gaps, making it incomplete for an agent to invoke correctly without external assumptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 50% coverage (only 'json' is described, not 'indent'). The tool description adds no clarity for the 'indent' parameter—it only reinforces 'JSON string.' Since schema coverage is low, the description should compensate by explaining the second parameter, but it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: 'Validate and format a JSON string.' It clearly indicates the tool processes JSON input and suggests both validation and formatting. However, 'format' is somewhat ambiguous (pretty-print vs minify), and it doesn't distinguish from similar tools like csv_to_json, though the resource is explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 sibling tools, exclusions, or prerequisites. The lack of any context leaves the agent to infer applicability purely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.