Skip to main content
Glama

BRAINIAC CRM Data Intelligence

Match contacts to companies

crm-intelligence_contact-relationship-match

Link each contact to a company that was supplied in the same request, by company-name key or email domain. A company that was not supplied is not created. Price $0.05 USDC. POST /api/v1/crm-intelligence/contact-relationship-match. 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-relationship-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
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, the description carries the full burden and does disclose real operating traits: a $0.05 USDC price, a 402 response for unpaid calls that do not run, and a non-creation side-effect guarantee. It still omits whether the tool persists relationships to any external CRM, how ties or multiple candidate companies are resolved, and whether repeat calls are idempotent.

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 matching behavior before price and transport details. The endpoint path partially restates the tool name, but the payment and 402 lines earn their space as operational context.

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?

No output schema and no annotations mean the description must cover both behavior and inputs, and it covers only the former partially. For a five-parameter tool with three alternate input encodings and nested objects, the absence of any note on which input channel to use or what the match result looks like is a meaningful gap.

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 five parameters with nested contact and company objects, and the description only alludes to matching keys ('company-name key or email domain'), which maps loosely to contacts.company/email and companies.name/domain. It says nothing about the csv, file, and json input alternatives or how they relate to the inline arrays, leaving the agent to guess which input form is expected when nothing is marked required.

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 pair — link contacts to companies — and adds a scope qualifier ('a company that was supplied in the same request') that separates it from enrichment or normalization siblings. It never names an alternative tool explicitly, so differentiation is implicit rather than stated.

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 the constraint that only supplied companies are considered and unsupplied ones are not created, which tells the agent the prerequisite inputs. There is no explicit when-to-use vs when-not guidance and no pointer to sibling tools such as company-normalize for cases where the company is missing from the request.

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