Skip to main content
Glama

BRAINIAC API Integration Intelligence

Diagnose an integration

integration_diagnose

Generate a schema from examples, validate the payload, map fields that exist, compare contracts, and apply documented transforms. No external API is called. Price $0.12 USDC. POST /api/v1/integration/diagnose. 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_diagnose"
  }
}

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.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries useful behavioral weight: it discloses that no external API is invoked (no external side effects), states the cost ($0.12 USDC), names the endpoint, and documents the failure mode that unpaid calls return 402 and do not execute. What it omits is what the result contains and whether all five operations always execute or only those whose inputs are supplied.

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?

Four short sentences, capabilities front-loaded, then constraints and payment terms; nothing is padded. The laundry-list phrasing of the first sentence makes the scope harder to grasp than a single leading statement of purpose would.

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 14-parameter, zero-required, deeply nested tool with no output schema and no annotations, the description is far too thin: it explains neither which inputs trigger which capability nor what the response looks like. An agent could form the request only by reverse-engineering the JSON schema alone.

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?

Schema description coverage is 0% across 14 parameters with deep nesting and a polymorphic operations array, so the description would need to compensate and does not name a single parameter. The capability list only loosely hints at groupings (examples→schema, source/target→map, before/after→compare, operations→transform), leaving the agent to guess the mapping and whether parameters are combinable.

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

Purpose3/5

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

The description enumerates five capabilities (schema generation, payload validation, field mapping, contract comparison, transform application) but never states what the tool actually returns or whether it runs all five or a subset selected by input. It reads as a bundle of sibling capabilities rather than a single well-defined operation, and it makes no attempt to distinguish itself from the named siblings that do each of those things individually.

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 at all: no indication of when to call this composite tool versus integration_json-schema-generate, integration_json-schema-validate, integration_field-map-generate, integration_contract-compare, or integration_payload-transform individually. The remaining sentences cover transport, pricing, and payment failure semantics, not usage selection.

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