Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getTeam

Read-onlyIdempotent

Fetches a Follow Up Boss team by ID so you can view team details for CRM workflows and reporting.

Instructions

Get a team 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": "getTeam"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTeam 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. The description adds nothing beyond that — no note on behavior when the ID does not exist, no indication of what fields come back, no permission context.

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?

One short, front-loaded sentence with no filler or repetition. It is efficient, though that brevity comes at the cost of any real substance.

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 single-parameter read tool, annotations cover its safety profile, and the schema documents the only argument, so minimal prose is defensible. However, with no output schema, the description gives no hint about the returned team object, leaving a modest gap.

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% and the single parameter is documented as "Team ID", so the schema carries the load. The phrase "by ID" in the description adds no meaning beyond that, which is the baseline 3 case for a fully documented single-parameter schema.

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 reads "Get a team by ID" for a tool named getTeam, so it largely restates the name. It does add the small clarifying detail that lookup is keyed on an ID, but it offers no differentiation from siblings such as listTeams, getGroup, or getTeamInboxes.

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 and no mention of when to prefer this over listTeams or getGroup. An agent must infer that this is the single-record lookup, with no explicit alternative routing.

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