Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createAppointmentType

Create a new appointment type in Follow Up Boss CRM by setting its name and sort position. Account owners can use it to define scheduling categories.

Instructions

Create an appointment type (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": "createAppointmentType"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoType 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.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world write. The description adds one genuinely new behavioral fact beyond them: the account-owner authorization requirement. It says nothing about what is created, whether duplicates are rejected, or what the call returns, so the addition is useful but thin.

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 front-loaded sentence with no filler, and the permission caveat is placed immediately after the action. It is efficient, though the same brevity is the source of the definition's other gaps.

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 two-optional-parameter create tool with full schema coverage and annotations, the essentials are present, but with no output schema the agent has no idea whether the created appointment type (and its ID) is returned. Nothing on duplicate-name behavior or failure modes is given either.

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%, so name and orderWeight are already documented as "Type name" and "Sort position". The description adds no syntax, format, length, or defaulting information beyond that, so the baseline of 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?

"Create an appointment type" gives a specific verb plus resource, which cleanly separates it from getAppointmentType, updateAppointmentType, and listAppointmentTypes in the sibling set. It stops short of explicitly naming those siblings, but the verb alone is enough for an agent to route correctly.

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?

The only guidance is the parenthetical "account owner only", which is a permission constraint rather than a when-to-use rule. There is no statement of when to create a new type versus modifying an existing one with updateAppointmentType, and no prerequisites or exclusions are given.

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