Skip to main content
Glama
Sign In
customer-replies-mcp-server

customer-replies-mcp-server

by alsaltitop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Compose Customer Reply

replies_compose_reply
Read-onlyIdempotent

Fill template variables with real customer data, such as name, device model, and repair status, to generate a ready-to-send reply.

Instructions

Render a ready-to-send customer reply by filling a template's {{variables}} with real values.

Args:

  • template_id (string): id from replies_search_templates

  • variables (object): map of variable name -> value, e.g. { "customer_name": "أحمد", "device_model": "iPhone 13", "status": "بانتظار قطعة الشاشة", "eta": "غداً الساعة 5 مساءً" }

Returns: { text, missingVariables }. If missingVariables is non-empty the reply still contains raw {{placeholders}} — fill them and call again, or ask the user for the values.

Example: compose a status update in Arabic for customer أحمد about his iPhone 13.

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": {
      "template_id": "<template_id>"
    },
    "name": "replies_compose_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
variablesNoVariable name -> value map. Values are inserted verbatim.
template_idYesTemplate id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. Description adds context about return structure (text and missingVariables) and the need for re-call if placeholders remain, which is beyond annotations.

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?

Extremely concise with no wasted words. Purpose is front-loaded, followed by clear parameter descriptions and an example.

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?

Despite no output schema, description compensates by explaining the return object with text and missingVariables. Provides a concrete example. Complete enough for a tool with 2 params.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value by linking template_id to replies_search_templates, providing Arabic example for variables, and explaining missing variables behavior.

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

Purpose5/5

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

Description clearly states the tool renders a ready-to-send reply by filling template variables. It uses a specific verb ('render') and distinguishes from sibling tools like replies_search_templates.

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

Usage Guidelines4/5

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

Provides clear guidance on using the tool after selecting a template and filling variables. Explains how to handle missing variables by calling again or asking user. Lacks explicit when-not-to-use or alternatives comparison.

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