Skip to main content
Glama

BRAINIAC CRM Data Intelligence

Normalize CRM companies

crm-intelligence_company-normalize

Normalize company names, domains, phone numbers, and addresses from a CSV or JSON company export. A trailing legal suffix stays in the name and is used only as a match key. Price $0.03 USDC. POST /api/v1/crm-intelligence/company-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_company-normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
companiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose useful traits: pricing ($0.03 USDC), the POST endpoint, and that unpaid calls return 402 without executing. It still omits what the operation actually returns, whether it writes anything back, idempotency, and rate 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?

Four short sentences, front-loaded with what is normalized, followed by the suffix rule, billing, and the 402 caveat. No filler, though the raw endpoint path is arguably low-value for an agent.

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?

For a four-param tool with nested objects, no annotations, and no output schema, the description covers purpose and billing but leaves the accepted input shape and return values unstated. It is adequate to recognize the tool but not to call it correctly without trial.

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% with four top-level params, and the description only implies that CSV and JSON forms are accepted. It says nothing about the nested companies array, the file object (base64/mediaType), or which of csv/json/file/companies are mutually exclusive, so an agent must guess the input shape.

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?

States a specific verb and resource: normalize company names, domains, phones, and addresses. The resource (company) implicitly distinguishes it from crm-intelligence_contact-normalize, but the description never explicitly differentiates it from duplicate-company-detect or other siblings.

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?

Describes the input source (a CSV or JSON company export) but gives no when-to-use / when-not-to-use guidance, no indication that this should run before or instead of duplicate-company-detect, and no note on what counts as a valid export.

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