Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateStage

DestructiveIdempotent

Change a stage's name or sort position in Follow Up Boss. Protected stages cannot be renamed; stage weights are automatically renumbered in steps of 1000.

Instructions

Update a stage's name or position. Stages with isProtected=true cannot be renamed. FUB renumbers all stage weights in steps of 1000.

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": "updateStage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStage ID
nameNoStage name (not allowed if isProtected)
orderWeightNoSort position

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / name / description
      Previous value: -"Stage name"New value: +"Stage name (not allowed if isProtected)"
    • addedInput schema / properties / orderWeight
      Added value: +{
      +  "description": "Sort position",
      +  "type": "number"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "name"
      -]New value: +[
      +  "id"
      +]
  2. First observedv1.1.1

TDQS

A3.9/5.0
Behavior4/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 partly covered. The description earns credit for two genuine additions beyond the structured fields: protected stages reject renames, and FUB renumbers all stage weights in increments of 1000 as a side effect of reordering. It does not explain why the operation is destructive (e.g. effects on attached deals) or what errors surface.

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, with the action statement front-loaded and the constraints following. No filler, no restatement of the tool name, nothing that could be cut.

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 small three-parameter mutation with no output schema, the definition covers the action, the permission rule, and the weight-renumbering side effect — enough to call it correctly. Missing pieces are minor: no statement of what happens when neither name nor orderWeight is supplied, and no hint about the response.

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?

Schema coverage is 100%, so the baseline would be 3 for schema-carried documentation. The description goes slightly beyond it by adding meaning to orderWeight — the backend renumbers all weights in steps of 1000, which tells the agent the value is relative rather than absolute — and by restating the isProtected constraint on name from the schema.

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?

Opens with a specific verb-plus-resource and the exact mutable fields: "Update a stage's name or position." That distinguishes it cleanly from createStage/getStage/listStages siblings. It stops short of explicitly differentiating it from other update* siblings or from moving deals between stages.

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?

Usage is only implied: an agent can infer this is the tool for renaming or reordering an existing stage, and the isProtected rule tells it when a rename will fail. There is no explicit when-to-use versus alternatives, no statement that at least one of name/orderWeight must accompany id, and no guidance on prerequisite lookups (getStage) before mutating.

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