Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getDealCustomField

Read-onlyIdempotent

Retrieve details for a specific deal custom field by ID, enabling accurate CRM data mapping and field configuration checks.

Instructions

Get a deal 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": "getDealCustomField"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesField 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, idempotentHint, non-destructive, and closed-world, so safety is fully covered structurally. The description adds nothing beyond that — no note on what happens for an unknown ID, whether archived fields are returned, or any auth/scope requirements.

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?

A single six-word sentence, front-loaded with the verb and resource. Nothing is wasted and nothing is padded.

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-param, read-only lookup with rich annotations and no output schema, the description covers the essential identity of the tool. The only omission is guidance on the list-vs-get choice, which keeps it from a 5.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself documenting 'Field ID'. The description's 'by ID' merely restates the schema, so the baseline 3 applies with no added semantics.

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?

States a specific verb and resource ('Get a deal custom field') plus the lookup key ('by ID'), which cleanly separates it from listDealCustomFields, createDealCustomField, and updateDealCustomField. It stops short of explicitly naming those siblings, so an agent must infer the single-item vs list distinction.

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 sentence telling the agent when to call this versus listDealCustomFields when the ID is unknown. The phrase 'by ID' only implies the precondition; no explicit when-to-use, exclusions, or error behavior is provided.

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