Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createDealAttachment

Attach an externally hosted file to a deal using its URI; requires registered system credentials and does not upload or host the file in Follow Up Boss.

Instructions

Attach an externally hosted file to a deal by URI. Restricted to registered systems (needs FUB_SYSTEM and FUB_SYSTEM_KEY). FUB does not host uploads here; omitting uri returns 403.

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

Input Schema

NameRequiredDescriptionDefault
uriYesURI of an externally hosted file.
dealIdYesID of the deal to attach to.
fileNameYesName of the file.
fileSizeNoSize of the file in bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.0
    • changedInput schema / properties / dealId / description
      Previous value: -"Deal ID"New value: +"ID of the deal to attach 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: -"File size"New value: +"Size of the file in bytes."
    • changedInput schema / properties / fileSize / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / uri / description
      Previous value: -"File URI"New value: +"URI of an externally hosted file."
  2. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing authentication prerequisites (FUB_SYSTEM and FUB_SYSTEM_KEY) and a concrete failure mode ('omitting uri returns 403'). It omits idempotency/duplicate behavior, which matters given idempotentHint=false, but the auth and error disclosure is substantial added value.

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?

Three short sentences, each carrying distinct information: purpose, authentication restriction, and error behavior. No redundant restatement of the name or schema.

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?

For a mutating tool with no output schema and non-idempotent semantics, it covers purpose, auth requirements, and failure behavior adequately. It could have noted duplicate-attachment behavior or what happens on re-attachment, but nothing critical for a correct call is missing.

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%, so all four parameters are already documented. The description adds that uri must point to an externally hosted file, reinforcing the schema's wording, but says nothing about fileName or fileSize beyond the schema. Baseline 3 is appropriate.

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+resource ('Attach an externally hosted file to a deal by URI') with clear scope. It does not explicitly distinguish itself from siblings like updateDealAttachment or createPersonAttachment, so it falls short of 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 Guidelines3/5

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

The description implies when to use it ('externally hosted file by URI') and notes FUB does not host uploads here, which steers agents away from an upload flow. However, it never names an alternative tool or states when to prefer one, leaving routing to inference.

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