Skip to main content
Glama

BRAINIAC CRM Data Intelligence

Audit CRM data quality

crm-intelligence_data-quality-audit

Report missing names, invalid emails, short phone numbers, missing companies, and duplicate records. A company is not inferred from an email domain. Price $0.04 USDC. POST /api/v1/crm-intelligence/data-quality-audit. 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_data-quality-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
contactsNo
companiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight: it discloses cost ($0.04 USDC), the HTTP endpoint, the 402 payment-gate failure mode, and the non-obvious rule that a company is not inferred from an email domain. It does not state that the operation is read-only/non-mutating, nor describe the shape of the returned report or any 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?

Four short sentences with the defect list front-loaded, then the domain-inference caveat, then pricing and transport details. No filler, though the endpoint path is arguably redundant with what a client already knows.

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

Completeness1/5

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

For a tool with five mutually exclusive input modes, nested payload structures, no annotations, and no output schema, the description omits the most decision-relevant facts: which input field to use when and what the audit report contains. An agent can only guess at invocation shape from the schema 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 description coverage is 0% across 5 parameters including two nested object arrays, so the description must compensate and does not. It never mentions that csv, json, file, contacts, and companies are alternative input channels, nor that max 500 contacts/companies apply. The email-domain note is the only hint about how inputs are interpreted.

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 ('Report') and enumerates the exact defect classes checked: missing names, invalid emails, short phone numbers, missing companies, duplicate records. An agent knows precisely what the tool produces. It does not distinguish itself from siblings like crm-intelligence_duplicate-contact-detect or duplicate-company-detect, which overlap on the duplicate portion.

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 when-to-use guidance and no exclusions relative to the sibling audit/duplicate-detect tools. The only usage-adjacent content is the payment precondition ('Unpaid calls return 402 and do not run'), which tells the agent about failure mode but not about tool selection.

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