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

customer-replies-mcp-server

by alsaltitop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Reply Template

replies_get_template
Read-onlyIdempotent

Retrieve a customer reply template by its ID, including the full body with variable placeholders. Get all details like category, title, language, and more.

Instructions

Get one template by id, including the full body with {{variable}} placeholders.

Args:

  • id (string): template id from replies_search_templates

Returns: full template JSON { id, category, title, language, tone, body, variables, tags, createdAt, updatedAt }.

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": "replies_get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate id, e.g. 'status-ar-1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing safe read behavior. The description adds value by specifying that the tool returns the full body with placeholders and lists the exact fields in the return JSON ({ id, category, title, ... }), which is 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: two short paragraphs. The first states the purpose and key feature (full body with placeholders). The second clearly lists arguments and return format. Every sentence is necessary and informative, with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that annotations provide safety traits, the input schema fully documents the single parameter, and the description includes the return structure, the tool definition is complete. No output schema exists, but the description compensates by listing the return fields.

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% with a description for the 'id' parameter including an example. The description adds semantic value by stating that the id comes from replies_search_templates, providing a source for the parameter and clarifying its origin.

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 clearly states the tool's purpose: 'Get one template by id, including the full body with {{variable}} placeholders.' It uses a specific verb ('Get') and resource ('template by id'), and the inclusion of 'full body with placeholders' distinguishes it from sibling tools like replies_search_templates which returns a list of template summaries.

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?

The description provides a usage hint: the 'id' argument should come from 'replies_search_templates', indicating a typical workflow of searching first then retrieving details. While it doesn't explicitly say when not to use, the set of sibling tools provides context. Clear guidance on parameter source is given.

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