Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listGroups

Read-onlyIdempotent

Retrieve lead-routing groups with pagination, sorting, and type filters to organize and route leads; lender accounts are excluded.

Instructions

List lead-routing groups (not accessible to lender accounts). Returns up to 100 per call; if _metadata.next is set, call again with next.

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

Input Schema

NameRequiredDescriptionDefault
nextNoCursor from _metadata.next of the previous call for the next page.
sortNoSort field; prefix with - for descending.
typeNoGroup type: Agent (admins and agents) or Lender (lender role users).
limitNoResults per call, max 100. Server sends 100 when omitted (FUB's own default is 10).
offsetNoRows to skip before returning results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Results per call, max 100. Server sends 100 when omitted (FUB's own default is 10).",
      +  "type": "integer"
      +}
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Cursor from _metadata.next of the previous call for the next page.",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip before returning results.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Sort field; prefix with - for descending.",
      +  "enum": [
      +    "id",
      +    "name"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Group type: Agent (admins and agents) or Lender (lender role users).",
      +  "enum": [
      +    "Agent",
      +    "Lender"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, yet the description still adds real value: an authorization constraint (lender accounts excluded), a page-size ceiling of 100, and the exact continuation rule for _metadata.next. It stops short of describing the shape of each group record, but that is a minor gap given the read-only listing nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, zero filler. The scope restriction is front-loaded and the pagination loop follows immediately, so an agent can read the whole contract in one pass.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, no required fields, and no output schema, the description supplies the pagination mechanism and the access restriction that an agent would otherwise have to discover by trial. Adding the group object's key fields would close the remaining gap, but nothing needed to invoke the tool correctly is missing.

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%, including enum semantics for sort and type and the limit default behavior, so the schema carries the parameter burden and baseline 3 applies. The description's only added semantics is tying the next parameter to _metadata.next of the prior response, which is genuinely useful but already implied by the schema text.

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 ("List lead-routing groups") plus an access-scope qualifier ("not accessible to lender accounts"), which is more precise than a bare name restatement. It does not explicitly distinguish itself from lookalike siblings such as listRoundRobinGroups, listTeams, or listPonds, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and the access note, and the description does give concrete follow-up guidance for pagination (re-call with next when _metadata.next is set). However, it never says when to prefer this over listRoundRobinGroups or listTeams, nor does it state prerequisites beyond the lender-account exclusion.

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