Skip to main content
Glama
alsaltitop

customer-replies-mcp-server

by alsaltitop

Add Reply Template

replies_add_template

Creates a new customer reply template with automatically extracted placeholders. Specify category, language, tone, and body with {{variable}} syntax to generate reusable responses.

Instructions

Create a new reply template. Placeholders in body use {{variable}} syntax; variables are auto-extracted from the body.

Args:

  • id (string): unique slug, e.g. 'promo-ar-1'

  • category (string): one of greeting, price_inquiry, diagnosis, repair_status, ready_for_pickup, delay_apology, warranty, complaint, unrepairable, data_disclaimer, part_unavailable, location_hours, payment, follow_up

  • title (string)

  • language ('ar'|'en')

  • tone ('formal'|'friendly')

  • body (string): reply text with {{placeholders}}

  • tags (string[], optional)

Returns: the created template JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique template id
bodyYesReply body with {{variable}} placeholders
tagsNo
toneYesReply tone
titleYes
categoryYesTemplate category
languageYesTemplate language: 'ar' Arabic or 'en' English
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds valuable behavioral context, such as that placeholders use {{variable}} syntax and variables are auto-extracted from the body. This goes beyond what annotations provide.

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?

The description is concise: a clear first sentence explaining the purpose, followed by a brief note on placeholders, then a compact argument list. No superfluous text; every part contributes to understanding.

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?

The tool has 7 parameters, 6 required, and no output schema. The description covers purpose, parameter semantics, and placeholder behavior. It could mention return format more explicitly, but given no output schema, the note 'Returns the created template JSON' suffices.

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 71%. The description lists parameters with explanations, but many details (e.g., enums for category, tone, language) are already in the schema. It adds some value with an example for 'id', but overall it doesn't significantly enrich beyond the schema.

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?

The description explicitly states 'Create a new reply template' and adds specific details about placeholder syntax and auto-extraction. The verb 'create' clearly distinguishes this from sibling tools like 'replies_update_template' and 'replies_delete_template'.

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?

The description implies that this tool is for adding new templates, but does not explicitly state when to use it versus alternatives like 'replies_update_template' or 'replies_search_templates'. It lacks explicit when-not-to-use guidance or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alsaltitop/customer-replies-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server