Skip to main content
Glama

BRAINIAC CRM Data Intelligence

Normalize CRM contacts

crm-intelligence_contact-normalize

Normalize names, emails, phone numbers, company names, and addresses from a CSV or JSON contact export. Original values stay beside the normalized values. Price $0.03 USDC. POST /api/v1/crm-intelligence/contact-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": "crm-intelligence_contact-normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
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, the description carries the full burden and does well: it discloses that original values are preserved beside normalized ones (non-destructive), the cost ($0.03 USDC), and the failure mode (unpaid calls return 402 and do not run). It omits what normalization rules actually apply and any rate or size limits.

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?

Three short sentences, front-loaded with the operation and inputs before the commercial and failure-mode details. The raw endpoint path is slightly redundant but earns its place for agents bridging to HTTP; nothing else is padding.

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 a data-transforming paid endpoint with four undocumented parameters and no output schema; the description partially compensates by promising original-plus-normalized values in the result. However, it leaves the contacts array and file upload paths entirely unexplained, which is a material gap for an agent choosing among input modes.

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 four parameters, including a nested file object and a contacts array of objects with 13 properties. The description only implies the csv and json parameters via 'CSV or JSON contact export' and never mentions the contacts array or the file object's mediaType/fileBase64 requirements, so it fails to 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 names a specific verb (normalize) and resource (contacts) and enumerates the field types it touches: names, emails, phone numbers, company names, addresses. That distinguishes it from siblings like company-normalize by scope of records, though it never explicitly contrasts against them.

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 implied by 'from a CSV or JSON contact export', which tells the agent the accepted input shape, but there is no statement of when to prefer this over duplicate-contact-detect, data-quality-audit, or company-normalize. No exclusions or prerequisites beyond the payment note.

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