Skip to main content
Glama

BRAINIAC API Integration Intelligence

Generate a field map

integration_field-map-generate

Map a path that exists on both sides, or a field name that matches one leaf on each side after splitting camel case and snake case. No value is copied. Price $0.05 USDC. POST /api/v1/integration/field-map-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_field-map-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

C2.7/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 usefully discloses that no values are copied, that the call costs $0.05 USDC, and that unpaid calls return 402 without running. It does not explain authorization, idempotency, output behavior, or other side effects an agent might need.

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 short and front-loads the core mapping behavior before operational details. The first sentence is dense but purposeful, and the remaining sentences add useful constraints without excessive repetition.

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 complex tool with 14 parameters, nested objects, no annotations, and no output schema. The description covers the high-level purpose, cost, and payment failure mode, but it omits the input composition rules and parameter roles needed to invoke the tool confidently.

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 input schema has 14 parameters with 0% description coverage, including complex nested objects and multiple mutually exclusive input fields. The description does not explain any parameter, so an agent must infer the meaning of source, target, before, after, schema, operations, and the file/json inputs entirely from the 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 explains the mapping logic specifically: matching existing paths or field names across camelCase and snake_case. It clearly implies generation of a field map and adds the constraint that no values are copied. It does not differentiate the tool from siblings such as payload-transform or contract-compare.

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 use this tool versus alternatives. Payment and failure behavior are described, but the definition does not explain which input combinations are appropriate or when another sibling tool should be preferred.

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