Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getCustomField

Read-onlyIdempotent

Fetch a custom field by ID from Follow Up Boss CRM to inspect its details and configuration.

Instructions

Get a custom field 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": "getCustomField"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCustom field 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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes nothing beyond that — no note on what happens when the ID is missing or belongs to a different field type, and no indication of response 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?

One short sentence with the resource and lookup key front-loaded, and no wasted words. It is arguably under-specified rather than verbose, but structurally it is clean.

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 one-parameter read tool with complete annotations and full schema coverage, this is just barely enough to call correctly. The absence of any hint about the returned field object or its relationship to getDealCustomField keeps it at minimum viable.

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?

The single parameter is fully documented in the schema (100% coverage) as "Custom field ID", and the description's "by ID" simply mirrors that. Baseline 3 applies when the schema already carries parameter meaning and the description adds nothing further.

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 custom field") and scopes it to a single-ID lookup, so the operation is unambiguous. It does not, however, distinguish itself from the sibling getDealCustomField, leaving an agent to guess which of the two retrieves the field it wants.

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, no mention of the alternative tools (listCustomFields, getDealCustomField), and no stated prerequisites or failure conditions. An agent must infer entirely from the name that this is the fetch-by-ID path.

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