Skip to main content
Glama

Customer message send

customer_message_send

[Support desk] Propose a short message to a customer phone (WhatsApp with an approved template, SMS when WhatsApp cannot be used): order_placed (an order confirmed with cash on delivery: values order, total), support_message (free text about an order: values order, text of 1-3 sentences) or parcel_status (values order, shipped, status). The greeting is always "doamna/domnule" + surname from values.name. Simulated first; nothing is sent until the seller approves. Works on: Support desk.

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": {
      "phone": "<phone>",
      "kind": "<kind>",
      "values": "<values>"
    },
    "name": "customer_message_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
phoneYes
valuesYes
accountNoAccount id from list_accounts. Optional when only one account is connected.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds the crucial behaviour that this is simulated first and nothing reaches the customer until the seller approves, plus channel constraints and the fixed greeting format. It does not say whether repeated calls create duplicate proposals, which matters given idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph, but it is front-loaded with the verb and channel rule and then structured as an explicit enumeration of kinds, so it is easy to scan. Slightly compact for the amount of enumerated detail, though every clause carries information.

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 4-parameter, nested-object mutation tool with an output schema, the description covers the simulation/approval gate, channel routing, kind-specific payloads and the greeting rule. Missing phone-number format guidance and duplicate-call behaviour are the only notable omissions.

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 description coverage is only 25% (only 'account' documented), but the description compensates well by mapping which values sub-fields belong to which kind (order/total, order/text, order/shipped/status) and explaining how values.name feeds the greeting. Remaining gaps are the phone format and the expected string formats for total/status/shipped.

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?

States a specific verb and resource ('Propose a short message to a customer phone') plus the two delivery channels (WhatsApp with approved template, SMS fallback) and enumerates the three message kinds with the fields each requires. An agent can tell exactly what this does and how it differs from an invoice/courier send sibling.

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?

Gives per-kind selection conditions (order_placed for confirmed COD orders, support_message for free text about an order, parcel_status for shipment status) and a channel preference rule (WhatsApp first, SMS only when WhatsApp is unavailable). It does not name explicit alternatives or when-not-to-call cases, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources