Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

addPersonToActionPlan

Assign a person to a Follow Up Boss action plan using person and action plan IDs, so you can start them on a defined follow-up sequence.

Instructions

Add a person to an action plan

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": {
      "personId": "<personId>",
      "actionPlanId": "<actionPlanId>"
    },
    "name": "addPersonToActionPlan"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesPerson ID
actionPlanIdYesAction plan ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare that this is a non-readonly, non-destructive, non-idempotent, closed-world mutation. The description adds no additional behavioral context such as what happens if the person is already in the action plan, required permissions, or side effects.

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?

The description is a single, front-loaded sentence with no unnecessary wording. It is exactly as concise as possible for the stated purpose.

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?

The tool is simple with two required parameters, full schema descriptions, and annotations covering safety and idempotency. However, the description does not explain return behavior, duplicate handling, or permissions, leaving some completeness gaps for a mutation tool.

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% for both required parameters, so the schema already documents personId and actionPlanId. The description adds no extra meaning beyond the schema, which matches the baseline of 3 for high coverage.

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 states a specific verb and resource: add a person to an action plan. It is clear what the tool does, though it does not explicitly differentiate itself from similar sibling operations such as addPersonToAutomation.

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 tool versus alternatives, nor any mention of prerequisites or exclusions. An agent must infer the appropriate context from the tool name alone.

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