Skip to main content
Glama

dev_tools_json_validate

[$x402 pago por llamada] Valida si un texto es JSON sintácticamente correcto. Siempre responde 200; el resultado va en el campo valid (true/false), nunca produce un error HTTP.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dev_tools_json_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: it discloses the always-200 contract, that the result surfaces in a `valid` boolean, and that no HTTP error is ever raised — genuinely useful non-obvious behavior. It omits what happens on a missing/invalid payload outside the payment path.

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

Conciseness5/5

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

Two tight sentences plus a bracketed payment marker, all front-loaded with the operation and then the response contract. Nothing redundant.

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

Completeness3/5

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

The description competently covers the return contract, but the input schema exposes no field for the text being validated, and the description never explains how the payload reaches the tool — a real gap for an agent trying to call it. Somewhat offset by the low complexity and zero required parameters.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter (x_payment) is already fully documented in the schema, so the baseline 3 applies. The description adds only the 'pago por llamada' framing and does not clarify where the JSON text to validate is actually supplied.

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?

States a specific verb and resource: validates whether text is syntactically correct JSON. That inherently separates it from dev_tools_json_format, but the description never names that sibling or any alternative explicitly, leaving the differentiation implicit.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb 'valida' — an agent can infer this is the linting check versus the formatter, but there is no explicit when-to-use, when-not-to-use, or alternative pointer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources