Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listRoundRobinGroups

Read-onlyIdempotent

Retrieve round robin groups and each group's next assigned user; sort by ID or name and filter by Agent or Lender type.

Instructions

List round robin groups, including each group's next round-robin user. Not accessible to lender accounts.

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort field; prefix with - for descending.
typeNoGroup type: Agent (admins and agents) or Lender (lender role users).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • 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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two pieces of real context beyond them: the response includes each group's next round-robin user, and lender accounts are excluded. It says nothing about pagination or result limits, but with annotations carrying the safety profile a 3 is fair.

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 short sentences with no filler, and the core purpose is front-loaded ahead of the access caveat. Nothing could be removed without losing information.

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?

For a simple, zero-required-parameter read tool with no output schema and fully documented parameters, the description covers purpose, payload shape and access restriction. It is slightly under-specified on how the type filter relates to the 'not accessible to lender accounts' restriction, which an agent may find ambiguous.

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 both parameters are enums with documented meanings, including the '-' prefix convention for descending sort. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ("List round robin groups") and adds the returned payload detail ("including each group's next round-robin user"). It does not explicitly differentiate itself from the sibling listGroups tool, which an agent could plausibly confuse with this one.

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?

The only guidance is an access constraint ("Not accessible to lender accounts"), which is useful but is a prerequisite rather than a when-to-use rule. There is no statement about when to prefer this over listGroups or how the sort/type filters should be chosen.

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