Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getEvent

Read-onlyIdempotent

Retrieve a single event by its ID from Follow Up Boss CRM to inspect event details.

Instructions

Get a single event by ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "getEvent"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the whole safety profile is covered by structured data. The description adds nothing beyond that: no return shape, no not-found behavior, no auth or scoping notes. It is effectively a restatement of the name.

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, front-loaded with the verb and free of padding. It is efficient, though its brevity borders on under-specification rather than economy.

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?

A simple one-parameter read tool with full annotation coverage does not need much, and no output schema exists to explain the return value. Still, for a getter the agent would benefit from knowing the event object's shape or what a missing ID yields, neither of which is covered anywhere.

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% with a single parameter whose schema text ('Event ID') is nearly identical to the description's 'by ID'. Baseline 3 applies since the schema carries the parameter semantics; the description adds no format, range, or sourcing guidance for the ID.

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 with scope: 'Get a single event by ID'. An agent knows exactly what the tool returns structurally. It does not differentiate itself from siblings like listEvents, getWebhookEvents, or listEmEvents, which makes the generic term 'event' slightly ambiguous in this API.

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 guidance at all — nothing telling the agent to prefer this over listEvents when an ID is known, and no prerequisites or failure conditions (e.g., what happens with an unknown ID). The single word 'single' hints at the list-vs-get distinction but does not state it.

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