Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listNotes

Read-onlyIdempotent

Retrieve notes, optionally filter by person ID, and paginate results to review contact history in Follow Up Boss CRM.

Instructions

List notes, optionally filtered by personId

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return
offsetNoPagination offset
personIdNoFilter notes by person ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.4

TDQS

B3.4/5.0
Behavior3/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 without the description. The description adds only the filter hint and says nothing about result ordering, default page size, or maximum limit, which would be genuinely useful behavior beyond the annotations.

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 sentence with zero filler and the core action front-loaded. It is efficient, though its brevity edges toward under-specification rather than maximal usefulness.

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 three-parameter read-only list tool with full schema coverage and rich annotations, the description is minimally sufficient. Still missing are pagination expectations and any hint about the shape of returned notes, which matter because there is no output schema.

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 all three parameters (limit, offset, personId) are already documented in the schema. The description restates the personId filter but adds no syntax, default values, or constraints beyond what the schema provides; 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 names a specific verb and resource ("List notes") and notes the optional filter. It clearly distinguishes a collection listing from the singular siblings getNote/updateNote/createNote, though it never names those siblings explicitly.

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 phrase "optionally filtered by personId" implies when the filter applies, but there is no explicit when-to-use guidance, no mention of when to prefer getNote for a single record, and no preconditions or exclusions stated.

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