Skip to main content
Glama

BRAINIAC API Integration Intelligence

Check version compatibility

integration_version-compatibility-check

Order dotted numeric versions and compare the supplied schemas. A version number alone is not treated as compatible. The payload is checked against the later schema. Price $0.04 USDC. POST /api/v1/integration/version-compatibility-check. 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_version-compatibility-check"
  }
}

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 burden. It does disclose useful behavior beyond the schema: the cost is $0.04 USDC, the endpoint is POST /api/v1/integration/version-compatibility-check, and unpaid calls return 402 without running. However, it says nothing about permissions, the returned result shape, or what a compatibility verdict contains, leaving meaningful behavioral gaps for a tool with no annotations.

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 front-loaded with the purpose, then behavior, then pricing and endpoint details in short sentences with little waste. The raw endpoint string and payment boilerplate are slightly mechanical but still earn their place by telling the agent that this is a paid POST call.

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 with 14 optional parameters, nested objects, an operations union type, and no output schema or annotations. The description omits any explanation of the parameters, the transform operations, or the result, so an agent cannot reliably call it correctly without further inference.

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, so the description must compensate and it largely does not. It mentions 'supplied schemas' and 'payload', loosely mapping to a few fields, but the before, after, source, target, fromVersion, toVersion, operations, and example fields are never explained, including the six-operation transform array whose semantics are not inferable from the schema alone.

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 and resource: it orders dotted numeric versions and compares supplied schemas, and checks a payload against the later schema. That is more than a restatement of the name, though it does not explicitly distinguish this from sibling tools such as integration_contract-compare or integration_json-schema-validate.

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. 'A version number alone is not treated as compatible' and 'the payload is checked against the later schema' hint at how the tool should be applied, but there is no explicit when-to-use guidance and no routing to alternatives among the sibling tools.

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