Skip to main content
Glama

BRAINIAC API Integration Intelligence

Validate a payload

integration_json-schema-validate

Check a payload against a supplied schema using the documented subset. Each failure has a JSON pointer. Unsupported keywords are reported and not applied. Price $0.04 USDC. POST /api/v1/integration/json-schema-validate. Unpaid calls return 402 and do not run.

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": "integration_json-schema-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
jsonNo
sideNo
afterNo
beforeNo
schemaNo
sourceNo
targetNo
exampleNo
payloadNo
examplesNo
toVersionNo
operationsNo
fromVersionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Because no annotations are supplied, the description carries the full behavioral burden, and it does meaningfully add: pricing ($0.04 USDC), that unpaid calls return 402 and do not execute, that unsupported schema keywords are reported rather than applied, and that failures carry JSON pointers. What it omits is what a successful response actually contains or how the 'documented subset' is defined, which matters for a tool that silently declines part of the schema.

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?

Five short sentences, front-loaded with the core action and followed by output shape, edge-case behavior, and cost. The bare 'POST /api/v1/integration/json-schema-validate' sentence adds little for an agent beyond transport detail, but nothing is padded or redundant.

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?

This is a high-complexity tool: 14 parameters with deep nesting, a six-variant operations union, and no output schema or annotations. The description covers cost and error semantics well but leaves the input contract almost entirely unaddressed, so an agent cannot confidently construct a call from the definition alone.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate for 14 parameters, and it essentially does not. It alludes only to 'payload' and 'schema'; the nested file object, examples, operations union (rename/copy/pick/omit/cast/default), before/after, source/target, and the side enum are left entirely unexplained.

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 gives a specific verb and resource: 'Check a payload against a supplied schema using the documented subset', which clearly separates it from sibling operations like json-schema-generate or payload-transform. It never names a sibling explicitly, so differentiation comes from the verb rather than routing guidance.

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?

There is no when-to-use guidance, no prerequisites, and no statement of when to prefer a sibling tool. More importantly, with 14 parameters including schema/payload, before/after, source/target, and operations, the description gives no hint about which combination of inputs is required for a validation call versus a transformation or migration call.

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