Skip to main content
Glama

BRAINIAC API Integration Intelligence

Normalize an API response

integration_response-normalize

Trim string edges and sort object keys. Types are not changed, fields are not removed, and each change is listed. Price $0.03 USDC. POST /api/v1/integration/response-normalize. 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_response-normalize"
  }
}

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?

With no annotations supplied, the description does add real behavioral value: it guarantees types are unchanged, no fields are removed, and every change is reported, plus it discloses the price ($0.03 USDC), the endpoint, and 402 behavior for unpaid calls. It omits permissions/auth requirements and says nothing about payload size limits or how the change list is returned.

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?

Sentences are short and front-loaded with the operation before guarantees and commercial terms. No filler, though the pricing and endpoint lines could arguably be structured more compactly.

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?

A 14-parameter, deeply nested tool with no output schema and no annotations needs far more description: which parameters to supply, whether `operations` is required for the trim/sort behavior, and what the 'changes listed' output looks like. The commercial and safety notes are good, but the schema burden is almost entirely unaddressed.

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?

The schema has 14 parameters at 0% description coverage, including a large discriminated `operations` union (rename/copy/pick/omit/cast/default) and a shared `__schema0` anyOf type that appears across many fields. The description explains none of them — not `operations`, not `source`/`target`, not `side`, not `file` vs `json` — leaving the agent to infer selection and format entirely from the raw schema.

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 names the operation and its two concrete effects ('Trim string edges and sort object keys'), so an agent knows exactly what normalization means here. It does not name a sibling alternative such as integration_payload-transform, so differentiation from the catalog is left implicit.

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 statement of when to reach for this tool versus integration_payload-transform or integration_payload-validate, nor any precondition guidance. Usage is only inferable from the operation description itself.

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