Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getStage

Read-onlyIdempotent

Retrieve a Follow Up Boss CRM pipeline stage by its ID to view stage details.

Instructions

Get a stage 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": "getStage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/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 by structured fields. The description adds nothing beyond them — no note on whether a missing ID errors or returns null, and no hint about the returned stage object. With the bar lowered by annotations, this still adds no value.

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?

Six words, front-loaded with the verb and resource, with zero redundancy or filler. It is efficient, though its brevity borders on under-specification rather than tight writing.

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?

This is a simple one-parameter read with full annotation coverage and no output schema, so most of an agent's needs are met by structured fields. What remains missing is minor but real: what a "stage" is in this domain and how listStages relates to lookup by 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?

Schema coverage is 100% and the single parameter is documented as "Stage ID", so the description has nothing left to explain. The phrase "by ID" merely restates the schema, which matches the baseline 3 for a fully covered parameter set.

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

Purpose3/5

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

The description states a specific verb and resource ("Get a stage") plus the lookup key ("by ID"), which is clearer than a tautology. However, it offers no differentiation from the many sibling getters (getTemplate, getDeal, getPipeline) or from listStages, so it only reaches the minimum-viable bar.

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?

Usage is only implied: an agent can infer it should call this when it has a stage ID. There is no explicit when-to-use guidance, no mention that listStages is the alternative when the ID is unknown, and no prerequisites 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