Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createAppointmentOutcome

Creates a new appointment outcome in Follow Up Boss CRM, letting account owners define outcome names and sort position.

Instructions

Create an appointment outcome (account owner only).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "createAppointmentOutcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOutcome name
orderWeightNoSort position

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / orderWeight
      Added value: +{
      +  "description": "Sort position",
      +  "type": "number"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[]
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation profile is covered structurally. The description contributes the valuable auth constraint ('account owner only') but says nothing about duplicate-name behavior, whether orderWeight collisions matter, or what a successful call yields.

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 the resource and the permission constraint front-loaded; every word earns its place. It is efficient but borders on under-specified rather than being genuinely well-structured.

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?

This is a simple create tool with two optional params and no output schema, so expectations are modest. Still, the description leaves open whether 'name' must be unique, what the default orderWeight is, and what object comes back, which an agent calling it would want to know.

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 both 'name' and 'orderWeight' are already documented in the schema as 'Outcome name' and 'Sort position'. The description adds no further semantics (valid ranges, uniqueness, default ordering), so the baseline 3 applies.

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 and resource ('Create an appointment outcome'), which is clearly separable from siblings like listAppointmentOutcomes, getAppointmentOutcome, and updateAppointmentOutcome. It does not explicitly name a sibling or contrast with createAppointmentType, so it falls just 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 parenthetical '(account owner only)' gives a real precondition for use, which is more than nothing. However, there is no guidance on when to choose this over createAppointmentType or on update-vs-create disambiguation, and no explicit exclusions.

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