Skip to main content
Glama

Suppress CRM Records

crm-suppress

Use when the user wants to exclude companies or contacts already in their CRM from future DiscoLike searches — e.g., "don't show me companies I already have in HubSpot" or "skip people already in my Salesforce."

Snapshots the connected CRM and saves the result as an exclusion list.

kind="companies" excludes by domain. kind="contacts" resolves the CRM's contact emails against DiscoLike's contact index and excludes the matching people — CRM contacts whose email DiscoLike has never seen are skipped (they can't appear in results anyway).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "provider": "<provider>"
    },
    "name": "crm-suppress"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo'companies' excludes by domain; 'contacts' excludes people matched by emailcompanies
contextNoWhy you are calling this tool, in a few words. No names or emails.
providerYesCRM provider to snapshot
llm_modelNoYour model id, or "unknown".
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations it discloses that the tool takes an external CRM snapshot and persists an exclusion list (consistent with readOnlyHint=false, destructiveHint=false), and that unmatched CRM contacts are silently skipped because they can never appear in results. That skip behavior is exactly the kind of outcome an agent would otherwise misreport. It does not cover reversibility, re-run accumulation, or runtime cost of a full snapshot.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the triggering condition, then the mechanics, then the per-mode semantics — each paragraph does distinct work. There is no filler or repetition of the schema, and the example utterances are compact and diagnostic.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers invocation, mechanism, and mode differences adequately for a 5-parameter tool. The remaining gap is idempotency: annotations say idempotentHint=false, yet the description never says whether repeated suppression stacks or duplicates entries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum values are already documented in the schema, so the baseline applies. The description does add real meaning for kind='contacts' by explaining the email-resolution step and the dropping of contacts absent from the email index, but says nothing about provider scope (whole CRM, no filtering) or the bookkeeping params.

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 states a specific verb+resource: exclude CRM companies/contacts from future DiscoLike searches by snapshotting the connected CRM into an exclusion list. It also splits the two operating modes (domain-based for companies, email-matching for contacts). It does not distinguish itself from similarly-named siblings such as crm-audit-companies or crm-match-companies, so an agent must still infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit use case ('Use when the user wants to exclude...') and backs it with two realistic user phrasings, so the invocation context is easy to recognize. It gives no when-not guidance and names no alternative (e.g., save-exclusion-list) for users who want to manage exclusions without a CRM.

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