Skip to main content
Glama
SalesSuite MCP Server

SalesSuite MCP Server

Official

Get Deals

list_deals_by_contact
Read-onlyIdempotent

Retrieve deals associated with a specific contact, with optional pipeline filtering and pagination, to review contact-related sales opportunities.

Instructions

Get Deals.

Returns a list of deals

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": {
      "contactId": "<contactId>"
    },
    "name": "list_deals_by_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (0 is the first page)
pageSizeNoItems per page (1-100)
contactIdYesWhen the contact ID is provided, only deals associated with that contact are returned.
pipelineIdNoWhen the pipeline ID is provided, only deals from that pipeline are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

The annotations already establish a read-only, idempotent, non-destructive operation, and the description is consistent with them. It adds no behavioral context such as the contact-scoped result set, pagination behavior, empty-result behavior, or external-service considerations.

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

Conciseness2/5

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

The text is short, but its two statements are redundant and neither front-loads the useful contact-specific purpose. This is under-specification rather than effective conciseness.

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

Completeness2/5

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

The schema and annotations supply enough mechanics for a basic call, but the description is not complete enough for reliable tool selection in a large sibling set. With no output schema, it also gives no indication that the result is a contact-filtered, paginated deal list or how it differs from the other deal retrieval tools.

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?

All four parameters are documented in the schema, including page defaults and bounds, the contact UUID filter, and the optional pipeline filter, so the baseline is 3. The description adds no parameter semantics, such as emphasizing that contactId is required or explaining how the contact and pipeline filters combine.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says only "Get Deals" and "Returns a list of deals," which restates the title and gives a generic operation and resource. It omits the defining contact scope and does not distinguish the tool from list_deals, search_deals, find_deals_by_email, or get_deal.

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 guidance about when to retrieve deals for a known contact or when another deal tool is preferable. The required contactId and the sibling alternatives are left entirely to the schema and tool names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.