Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getDealAttachment

Read-onlyIdempotent

Retrieves a specific deal attachment by its ID so you can access or verify the file linked to a Follow Up Boss deal.

Instructions

Get a deal attachment 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": "getDealAttachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAttachment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered without description help. The description adds no behavioral context at all: nothing about permissions needed to view a deal attachment, file/size handling, or whether the attachment URL expires.

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?

A single short sentence with no wasted words and the resource front-loaded. It is efficient but borderline under-specified; nothing superfluous, though little is gained over the name alone.

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 a fully covered schema and complete annotations, the description is minimally sufficient to call it correctly. It is thin on what the returned attachment looks like (no output schema exists), which is the main remaining gap.

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 description coverage is 100% with a single required numeric 'id', so the schema carries parameter meaning. The phrase 'by ID' in the description adds no format, source, or scoping detail beyond what the schema already states, so the baseline 3 applies.

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

Purpose3/5

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

The description states a verb and resource ('Get a deal attachment') but is essentially the tool name restated, with only 'by ID' added. It doesn't distinguish this from the many other single-entity getters in the sibling list (getPersonAttachment, getDeal, getCall), beyond the resource noun embedded in the name itself.

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?

No when-to-use guidance, no mention of when to prefer listDeals/getDeal or create/updateDealAttachment instead. The only implied usage is the get_/list_ naming convention, which the description does not reinforce or explain.

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