Skip to main content
Glama

BRAINIAC CRM Data Intelligence

Report a CRM cleanup

crm-intelligence_database-cleanup-report

Combine normalized records, duplicate pairs, safe merge suggestions, caller-fact enrichment, relationship matches, and quality issues. No external CRM is changed. Price $0.12 USDC. POST /api/v1/crm-intelligence/database-cleanup-report. 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_database-cleanup-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
factsNo
contactsNo
companiesNo

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 well: it states no external CRM is changed, discloses the $0.12 USDC price, gives the endpoint, and explains that unpaid calls return 402 and do not execute. It omits what the response contains and any size/rate limits, but the cost and payment-gating disclosure is exactly the kind of context annotations would otherwise provide.

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 capability list before the operational constraints, with no filler. The raw endpoint path is marginally useful for direct API callers but is the least valuable sentence for an agent choosing a tool.

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 six-parameter, deeply nested, no-output-schema tool, the description covers cost, safety, and payment failure behavior but leaves the input contract unexplained. An agent knows what it gets and what it costs, but not what it must supply to get a successful run.

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 six parameters, several of them nested objects (contacts, companies, facts, file), so the description must compensate and does not. It never explains that csv/json/file are alternative input payloads, whether at least one input is required despite zero required parameters, or what the facts array's match/value pairing means.

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 composite operation and enumerates its outputs (normalized records, duplicate pairs, merge suggestions, enrichment, relationship matches, quality issues), which lets an agent recognize it as the aggregate of the sibling normalize/detect/audit tools. It stops short of explicitly stating it supersedes those siblings, but the resource and scope are unambiguous.

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: an agent can infer this is the one-shot 'do everything' call because the description lists the outputs of the individual sibling tools. There is no explicit when-to-use versus when-to-call-the-narrower-tools guidance, and no stated prerequisites such as a minimum input requirement.

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