Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateDealAttachment

DestructiveIdempotent

Update a deal attachment by ID, providing dealId, URI, and fileName on every call since Follow Up Boss requires them even when unchanged.

Instructions

Update a deal attachment by ID. FUB requires dealId, uri and fileName on every update, even if unchanged.

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>",
      "dealId": "<dealId>",
      "uri": "<uri>",
      "fileName": "<fileName>"
    },
    "name": "updateDealAttachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAttachment ID.
uriYesURI of an externally hosted file.
dealIdYesID of the deal the attachment belongs to.
fileNameYesName of the file.
fileSizeNoSize of the file in bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • changedInput schema / properties / dealId / description
      Previous value: -"Deal ID"New value: +"ID of the deal the attachment belongs to."
    • changedInput schema / properties / dealId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / fileName / description
      Previous value: -"File name"New value: +"Name of the file."
    • changedInput schema / properties / fileSize / description
      Previous value: -"Size"New value: +"Size of the file in bytes."
    • changedInput schema / properties / fileSize / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / id / description
      Previous value: -"Attachment ID"New value: +"Attachment ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / uri / description
      Previous value: -"URI"New value: +"URI of an externally hosted file."
  2. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally; the description usefully adds the mandatory-resupply rule. However, it does not disclose what 'destructive' means here — whether the existing file/URI is replaced, and what happens to optional fields like fileSize when omitted.

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?

Two short sentences with zero filler; the mandatory-field constraint is front-loaded immediately after the purpose statement where an agent will read it before building arguments.

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 destructive mutation with no output schema, the definition covers purpose and required inputs but leaves the mutation semantics vague: what is replaced, whether partial updates are possible, and what a successful response contains. Adequate to call correctly, not enough to predict consequences.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, and the description adds meaning the schema cannot express: the three core fields are required on every update even if their values are unchanged. It still says nothing about the optional fileSize behavior or whether omitting it clears the stored value.

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 ('Update') and resource ('deal attachment') with an ID-based targeting detail, which clearly separates it from createDealAttachment and getDealAttachment. It stops short of naming those siblings explicitly, so it lands just under a 5.

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?

The second sentence gives real operational guidance: dealId, uri and fileName must be resupplied on every call even when unchanged, which prevents a common failure mode. There are no exclusions or guidance on when to use an alternative (e.g., createDealAttachment for new files), so it is not a 5.

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