Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getPond

Read-onlyIdempotent

Retrieves a specific pond by its ID from Follow Up Boss CRM, enabling targeted lookup of pond data.

Instructions

Get a pond 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": "getPond"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPond 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, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds no behavioral context beyond that — no note on error behavior for a missing/invalid ID, no mention of what a pond record contains, and no output shape.

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 four-word sentence with the resource and lookup key front-loaded; nothing is wasted. It is efficient but borders on under-specification rather than demonstrating tight structure.

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 full schema coverage, the description is minimally sufficient to call the tool. It still leaves gaps around ID sourcing and return content (no output schema exists to compensate), so it is adequate but not complete.

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 required parameter documented as "Pond ID", so the schema already does the work. The phrase "by ID" merely restates the schema rather than adding format, range, or sourcing guidance, making the baseline 3 appropriate.

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 and resource ("Get a pond") and the keying mechanism ("by ID"), so the agent immediately knows this is a single-record fetch. However, it does not distinguish itself from siblings like listPonds, createPond, or updatePond, which would have raised this to a 5.

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 explicit when-to-use guidance, no statement of prerequisites beyond the implied need for an ID, and no pointer to listPonds for discovering IDs. The correct usage is inferable from the name alone, but the description contributes nothing to that 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