Skip to main content
Glama

BRAINIAC API Integration Intelligence

Transform a payload

integration_payload-transform

Apply rename, copy, pick, omit, cast, and default in order. A missing source is reported and not invented. A default is written only when the path is absent. Price $0.05 USDC. POST /api/v1/integration/payload-transform. 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_payload-transform"
  }
}

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
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses the pipeline ordering, that missing sources are reported rather than fabricated, that defaults only fire on absent paths, the flat $0.05 USDC price, and that unpaid calls return 402 without executing. It stops short of covering mid-pipeline failure behavior or output shape, but the payment and error semantics are unusually well surfaced.

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 operation list and then behavioral constraints, with no filler. The trailing HTTP endpoint and price details are compact and arguably necessary given no annotations.

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 tool with 14 parameters, nested objects, 0% schema coverage, and no output schema, the description covers behavior well but input semantics barely at all. An agent would not know how to populate the many oneOf/anyOf input slots from this text 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 coverage is 0% across 14 parameters, several of which are nested (file object, operations array of typed op objects, before/after/schema/example slots). The description explains only the operation vocabulary and the default-op rule; it says nothing about what json vs payload vs source/target vs before/after mean or how file input differs from inline json, leaving most of the surface 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 description names a specific set of transformation operations (rename, copy, pick, omit, cast, default) applied to a payload and states they run in order, which is more concrete than the title alone. It does not, however, distinguish this from siblings like integration_response-normalize or integration_field-map-generate, so an agent must infer the boundary.

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 explicit guidance on when to reach for this tool versus the alternative normalization, field-map, or schema tools in the sibling set. The order-of-operations note is about internal behavior, not about when to choose this tool.

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