Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listUnclaimed

Read-onlyIdempotent

List unclaimed people in Follow Up Boss ponds that are not yet assigned, with limit and offset for pagination. Retrieve unassigned leads to claim and route to agents.

Instructions

List unclaimed people (in ponds, not assigned)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return
offsetNoOffset for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/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 the safety profile is fully covered without the description's help. The description contributes the semantic definition of "unclaimed" (pond membership without assignment), which is real added context, but says nothing about ordering, default page size, or what a returned person looks like. Modest value on top of annotations warrants a 3.

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 short line with zero filler and the disambiguating detail ("in ponds, not assigned") placed immediately after the resource. Well front-loaded; the only cost is that the brevity reflects under-specification handled elsewhere rather than waste.

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, two-optional-param read tool with full annotation coverage and no output schema, the minimum is nearly met. Still, an agent gets no sense of default page size, ordering, or whether unclaimed status is scoped to the caller's ponds, which are the questions that actually affect a correct call.

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% – both limit and offset are documented in the schema itself. The description adds nothing about pagination behavior, defaults, or maximum limits, so the baseline 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 ("List") and a specific resource ("unclaimed people"), then defines the term inline: people "in ponds, not assigned." That distinguishes it from the broad listPeople sibling, though it never names an alternative outright.

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 or when-not-to-use guidance, no mention of claimPerson or listPeople as alternatives, and no statement about prerequisites or defaults. The parenthetical definition implies the domain but the agent must infer when this list is the right call.

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