Skip to main content
Glama

BRAINIAC API Integration Intelligence

Generate a JSON schema

integration_json-schema-generate

Build a schema from supplied examples. Required properties are keys present on every example. Whole numbers are integer. Additional properties stay allowed. Price $0.04 USDC. POST /api/v1/integration/json-schema-generate. 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-generate"
  }
}

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

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses payment behavior (0.04 USDC and 402 on unpaid calls) and three generation rules about required properties, integer inference, and additional properties, but it omits permissions, output behavior, and how the many input modes affect execution.

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?

The description is front-loaded with the purpose and then gives compact rules, pricing, endpoint, and payment failure behavior. Every sentence earns its place without redundant restatement.

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 nested 14-parameter tool with no annotations, no output schema, and 0% parameter description coverage, this description is not complete enough. It covers some output inference and payment behavior but leaves the main input-selection and operation semantics unexplained.

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% across 14 parameters, so the description must compensate. It only hints at supplied examples and never explains file, json, side, before, after, schema, source, target, operations, or version parameters, leaving nearly all input meaning undocumented.

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 first sentence states a specific verb and resource: build a schema from supplied examples. This is clear enough to select the tool for schema generation, though it does not explicitly distinguish it from the sibling schema-validate tool.

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?

The description implies usage when examples are available, which is helpful context, but it provides no explicit when-not guidance or comparison with alternatives such as integration_json-schema-validate. The payment note is operational rather than usage guidance.

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