Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listPonds

Read-onlyIdempotent

Retrieve shared lead pools (ponds) from Follow Up Boss, up to 100 per call; use the returned next cursor to fetch additional pages.

Instructions

List ponds (shared lead pools). 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": "listPonds"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNoCursor from _metadata.next of the previous call for the next page.
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. Changed3 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"
      +}
  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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description still adds real behavioral information beyond them: the 100-result page cap and the exact continuation rule ("if _metadata.next is set, call again with next"), which tells the agent how to fully drain the collection.

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 the resource definition front-loaded and the pagination contract immediately after. No filler, no restatement of annotations or schema boilerplate.

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 read-only, three-parameter list tool with full schema coverage and rich annotations, the description covers the one thing the schema cannot: how to iterate pages until completion. Without an output schema, the mention of _metadata.next also hints at the response envelope shape, though the overall return structure remains only partly described.

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%, so the schema already explains next, limit and offset, including the server default of 100. The description reinforces the cursor loop semantics but adds nothing about offset or how limit interacts with paging, 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 names a specific verb and resource ("List ponds") and adds a useful gloss, "shared lead pools", that clarifies the domain term. It does not explicitly distinguish itself from getPond/createPond/updatePond or updatePond, so it falls short of a 5.

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?

Listing usage is implied by "List ponds" and the pagination instruction, but there is no explicit when-to-use or when-not-to-use guidance relative to getPond or the pond-mutating siblings. An agent can infer this is the enumeration call, but nothing in the text confirms that.

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