Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getAutomationPerson

Read-onlyIdempotent

Retrieve an automation-person entry by ID to inspect Follow Up Boss automation details and manage related workflows.

Instructions

Get an automation-person entry by ID

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

Input Schema

NameRequiredDescriptionDefault
idYesAutomationPerson ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond them — no behavior on missing IDs, no indication of what is returned, no note on permissions.

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 zero filler. It is efficiently sized, though its brevity borders on under-specification rather than optimal concision.

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 trivial one-parameter read tool with a fully described schema and complete read-only annotations, the description is minimally sufficient. It could still clarify the entity's relationship to automation/person resources and what happens for unknown IDs.

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?

There is a single parameter whose schema description ('AutomationPerson ID') has 100% coverage, so the schema already does the work. The description's 'by ID' only restates that, adding no format, range, or sourcing guidance (e.g., where such an ID is obtained).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb and resource ('Get an automation-person entry by ID'), which is enough to know it retrieves a single record. However, 'automation-person entry' is ambiguous jargon and the description gives no hint of the entity's fields or how it differs from siblings like listAutomationsPeople or getPerson.

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 when-to-use guidance, no statement of prerequisites, and no mention of alternatives such as listAutomationsPeople for enumerating entries. The agent must infer that this is the single-record lookup counterpart to the list tool.

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