Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getGroup

Read-onlyIdempotent

Retrieve a Follow Up Boss CRM group by ID to view its details and support contact or pipeline organization.

Instructions

Get a group 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": "getGroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGroup 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 readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds nothing beyond that — no note on not-found behavior, permission requirements, or what a 'group' contains.

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 tidy sentence with no waste and the operation front-loaded. It is short to the point of being under-specified rather than verbose.

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 simple one-parameter read tool with full annotation coverage this is roughly adequate, but with no output schema the description never indicates the shape of the returned group, and it omits the singular-vs-list contrast with listGroups.

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% with the single 'id' parameter documented as 'Group ID'. The description adds no format, range, or sourcing guidance beyond the schema, which is acceptable but minimal given the schema does all the work.

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 ('Get a group') constrained by 'by ID', so an agent knows it retrieves a single group. It does not differentiate itself from siblings like listGroups or getTeam beyond the implicit singular-vs-list distinction.

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?

No when-to-use guidance, no prerequisites, and no mention of listGroups as the alternative when the ID is unknown. The agent must infer the retrieval-vs-list distinction entirely from the tool name.

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