Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getThreadedReplies

Read-onlyIdempotent

Retrieve a single threaded reply by its own ID. To list a note's replies, fetch the note with includeThreadedReplies=true instead.

Instructions

Get ONE threaded reply by the reply's own ID. To list a note's replies, fetch the note with includeThreadedReplies=true instead.

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

Input Schema

NameRequiredDescriptionDefault
idYesReply ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / id / description
      Previous value: -"Item ID"New value: +"Reply ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  2. First observedv1.1.1

TDQS

A4.2/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 and determinism profile is fully covered by structured data. The description adds only scoping context (single item, retrieval not enumeration) and says nothing about error behavior for missing IDs or what the payload contains. Adequate but not additive beyond annotations.

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, front-loaded with the primary action and followed by the routing rule. No filler, no restatement of the tool name, nothing wasted.

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 one-parameter read tool with full annotation coverage and no output schema, the description supplies everything needed to select and invoke it correctly. The only unstated element is the shape of the returned reply, which is a minor gap for a tool this simple.

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 coverage is 100% and the single parameter is already documented as "Reply ID." The phrase "the reply's own ID" reinforces that this is not a note ID, which is mild disambiguation but not new syntax or format meaning. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get ONE threaded reply by the reply's own ID" gives a specific verb (get), a specific resource (threaded reply), and emphatic singular scope that separates it from any list-style retrieval. An agent can tell immediately this returns exactly one object, not a collection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names the concrete alternative and the condition that selects it: to list a note's replies, fetch the note with includeThreadedReplies=true. That removes the most likely misuse of this tool (calling it repeatedly to enumerate replies).

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