Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getCall

Read-onlyIdempotent

Fetch a Follow Up Boss call record by ID to inspect call details and activity history.

Instructions

Get a call 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": "getCall"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCall ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/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. The description adds nothing beyond that — no note on not-found behavior, permissions, or scope — so it contributes no behavioral context of its own.

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?

Five words, front-loaded with the verb and resource, with zero filler. It is efficient, though its brevity borders on under-specification rather than economy of expression.

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 trivial one-parameter read tool with rich annotations and no output schema, this is minimally sufficient. It is still thin on what an agent would want before calling — whether the response includes associated people or activity, and what happens on an invalid ID.

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?

There is a single required parameter documented at 100% schema coverage ('Call ID'), so the schema does the work and the description only echoes it with 'by ID'. No additional meaning (ID format, source, example) is supplied, which is the baseline for high-coverage schemas.

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 (Get) and resource (a call) plus the selector (ID), so the purpose is unambiguous. It does not, however, distinguish this from siblings like listCalls or getTextMessage by stating what kind of record a 'call' is or what is returned.

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 only implied: the 'by ID' phrasing signals a single-record fetch that requires a known ID, in contrast to listCalls. There is no explicit statement of when to use this versus listCalls, nor any note about behavior when the ID does not exist.

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