Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getDeal

Read-onlyIdempotent

Retrieve a Follow Up Boss deal by ID to view its details, stage, and pipeline status for CRM follow-up and reporting.

Instructions

Get a deal by ID

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": {
      "id": "<id>"
    },
    "name": "getDeal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDeal ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that – no error/not-found behavior, no note on how missing or deleted deals are handled, no indication of what a deal representation contains.

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?

Five words, front-loaded with the verb and resource, with zero filler or redundancy. Its brevity is efficient, though the same economy is what leaves the other dimensions thin.

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 one-parameter read tool with no output schema and full annotation coverage, this is barely adequate: an agent knows what to pass and that it is safe, but not what a returned deal object looks like or how failures surface. The complexity is low enough that the gaps are tolerable, not ideal.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents "Deal ID". The phrase "by ID" merely restates the schema and contributes no format or sourcing detail, which matches the baseline-3 expectation when schema coverage is complete.

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 ("Get") and resource ("a deal") and adds a lookup qualifier ("by ID") that separates it from listDeals. It stops short of distinguishing itself from the adjacent getDealAttachment/getDealCustomField/getDealCustomField siblings, so it is clear but not fully differentiated.

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 on when to use this versus listDeals, updateDeal, or the deal sub-resource getters. The agent must infer from the name alone that this is the single-record read path, with no stated prerequisites or exclusions.

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

Deploy Server

Other Tools