Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listEvents

Read-onlyIdempotent

Fetch CRM events newest first and filter by person, event type, or property to review activity and isolate specific records.

Instructions

List events, newest first by FUB default. Filter by person, event type, or property.

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

Input Schema

NameRequiredDescriptionDefault
nextNoCursor from _metadata.next of the previous page.
typeNoComma-separated types, e.g. 'Registration,Property Inquiry'. Full list = createEvent type enum.
limitNoResults per call. Default 10, max 100.
offsetNoRows to skip. Default 0. Prefer next for deep paging.
personIdNoOnly events for this person.
hasPropertyNotrue = only events with an associated property.
propertyAddressNoPartial-match search of property addresses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.0.0
    • changedInput schema / properties / hasProperty / description
      Previous value: -"Filter events that have property data"New value: +"true = only events with an associated property."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Results per call. Default 10, max 100."
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / next / description
      Previous value: -"Cursor for next page of results"New value: +"Cursor from _metadata.next of the previous page."
    • changedInput schema / properties / offset / description
      Previous value: -"Offset for pagination"New value: +"Rows to skip. Default 0. Prefer next for deep paging."
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / personId / description
      Previous value: -"Filter by person ID"New value: +"Only events for this person."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / propertyAddress / description
      Previous value: -"Filter by property address"New value: +"Partial-match search of property addresses."
    • changedInput schema / properties / type / description
      Previous value: -"Filter by event type"New value: +"Comma-separated types, e.g. 'Registration,Property Inquiry'. Full list = createEvent type enum."
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds the default ordering ('newest first by FUB default'), which is genuinely useful behavior not in the schema, but it says nothing about pagination limits, result volume, or error behavior for this open-ended listing.

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?

Two sentences, front-loaded with the action and default ordering, with no filler. The phrase 'by FUB default' is slightly opaque shorthand, but the definition is compact and easy to scan.

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 read-only list tool with full schema coverage and no output schema, the definition plus annotations give an agent enough to call it correctly. The only real gap is that nothing describes what a result looks like or how paging terminates, which the schema only partially covers via the 'next' cursor.

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 every parameter is already documented, including the 'next' cursor, limit defaults, and the comma-separated type syntax. The description only restates the filter dimensions at a high level and adds no syntax or precedence detail beyond the schema; 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?

States a specific verb and resource ('List events') plus the default sort order ('newest first by FUB default') and the three filter dimensions. It is clearly a listing tool, though it never names its closest sibling (getEvent for a single event) to draw the contrast 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?

Usage is implied by the filter list — an agent infers this is the tool for enumerating events filtered by person, type, or property. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as getEvent or listEmEvents, so routing depends on inference.

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