Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getUser

Read-onlyIdempotent

Retrieve a Follow Up Boss user by numeric ID to identify or reference the correct CRM user.

Instructions

Get a user 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": "getUser"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUser ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/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 that — no note on error behavior for unknown IDs, whether it returns null or throws, or permission requirements.

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 five-word clause with zero filler and the lookup key front-loaded. It is efficient, though so terse that no structure beyond the bare statement exists.

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 one-parameter read tool with complete schema coverage and full annotations, very little prose is required, so the gap is modest. The missing piece is disambiguation from the many similarly named retrieval siblings, which the description never addresses.

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?

The single parameter is fully described in the schema ("User ID", type number) at 100% coverage, and "by ID" in the description merely restates it. Baseline 3 applies since the schema carries the semantics with no added detail from the description.

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?

"Get a user by ID" names a specific verb (get) and resource (user) plus the lookup key, so the operation is unambiguous. It does not distinguish this from siblings such as getPerson, getCurrentUser, or listUsers, so an agent cannot tell from the text alone which retrieval tool applies.

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 exclusion versus getCurrentUser/getPerson/getPersonByEmail, and no stated precondition such as needing a known ID. The agent is left to infer that this is a direct single-record lookup by numeric ID.

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