Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

mergeTextMessageTemplate

Read-onlyIdempotent

Merges a text message template with a person's data and returns the rendered text without sending anything. Use it to preview personalized SMS content before sending.

Instructions

Merge a text message template with a person's data and return the rendered text. Does not send anything.

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": {
      "templateId": "<templateId>"
    },
    "name": "mergeTextMessageTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdNoPerson ID whose data fills merge fields (docs example uses mergePersonId)
recipientsNoRecipients. from is unused by FUB.
templateIdYesText message template ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID"New value: +"Person ID whose data fills merge fields (docs example uses mergePersonId)"
    • addedInput schema / properties / recipients
      Added value: +{
      +  "description": "Recipients. from is unused by FUB.",
      +  "properties": {
      +    "to": {
      +      "items": {
      +        "properties": {
      +          "name": {
      +            "description": "Recipient name",
      +            "type": "string"
      +          },
      +          "phone": {
      +            "description": "Recipient phone",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedInput schema / properties / templateId / description
      Previous value: -"Template ID"New value: +"Text message template ID"
    • changedInput schema / required
      Previous value: -[
      -  "templateId",
      -  "personId"
      -]New value: +[
      +  "templateId"
      +]
  2. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description still adds real value by explicitly guaranteeing no message is dispatched and by naming the return value (rendered text), which matters since there is no output schema. It omits edge-case behavior for unresolved merge fields or unknown template IDs.

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 with no waste; the core action is front-loaded and the non-send guarantee follows immediately. Nothing is redundant or padded.

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 simple read-only merge tool with a nested recipients object and no output schema, it covers purpose, return value, and side-effect absence. It leaves gaps around parameter interplay (why pass recipients when merging against a person) and failure modes, which matter for a nested-schema tool.

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%, so the three parameters are already documented, and the description adds nothing about templateId, personId, or the nested recipients object. Baseline 3 applies since the schema carries the parameter burden, though the description could have clarified how personId and recipients interact.

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 (merge a text message template with a person's data) plus the outcome (returns rendered text), which is far more informative than the bare tool name. It does not explicitly distinguish itself from the sibling mergeTemplate, so an agent must infer that one is for email/different template types.

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

Usage Guidelines3/5

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

"Does not send anything" implies the preview/inspection use case, which is useful guidance by implication. However, it never states when to choose this over mergeTemplate or createTextMessage, nor what prerequisites (e.g., a valid templateId) are needed.

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