Skip to main content
Glama

BRAINIAC CRM Data Intelligence

Enrich CRM records from input

crm-intelligence_record-enrichment-from-input

Copy caller-supplied facts into empty contact fields. A fact never overwrites a value that is already present, and no contact detail is invented. Price $0.04 USDC. POST /api/v1/crm-intelligence/record-enrichment-from-input. 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": "crm-intelligence_record-enrichment-from-input"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
factsNo
contactsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the no-overwrite and no-invention semantics, the $0.04 USDC price, the POST endpoint, and that unpaid calls return 402 without running. It still omits authentication requirements, what happens to facts that match no contact, and the response shape, but this is well above baseline for an unannotated mutation tool.

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, front-loaded with the core operation and its safety guarantee before cost and transport details. Each sentence carries information, though the raw endpoint path is of lower value to an agent than the surrounding semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is structurally complex (nested objects, five optional parameters, three input modalities) with no annotations and no output schema. The description adequately covers the write-safety profile and payment behavior but leaves the central question of how to compose the input parameters unanswered, which is the main gap for an agent trying to call it correctly.

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% and the tool has five top-level parameters, including three alternative input formats (csv, json, file) plus contacts and facts arrays. The description mentions 'caller-supplied facts' but never explains how csv/json/file relate to the facts array, whether contacts is required for matching, or which combination is valid given that no parameter is required. The description does not compensate for the coverage gap.

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 opens with a specific verb and resource: 'Copy caller-supplied facts into empty contact fields.' That is distinct from sibling normalization and duplicate-detection tools, which reformat or compare rather than fill blank fields. It stops short of explicitly naming an alternative, but the operation itself is unmistakable.

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 through behavioral constraints: facts go into empty fields, never overwriting existing values, and nothing is invented. There is no explicit 'use this when you have X and want Y' guidance, and no statement about which of the five input parameters is appropriate for which situation.

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