Skip to main content
Glama

Draft a customer email reply

draft_customer_email_reply

Asks Emporiqa to write a draft reply to one customer email, from the shop's catalogue, pages and order status, optionally following a note of what to say. Sends nothing: the draft waits in the store's Customer emails page for the team, and is ready in about a minute. Up to 4 drafts per email. Writing a draft is not billed. Needs the conversations permission and the store's switch for AI assistants in Settings > Security, and works only for stores the person owns.

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": {
      "store_id": "<store_id>",
      "email_id": "<email_id>"
    },
    "name": "draft_customer_email_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat the reply should say, in a few words. No numbers of 4 digits or more, email addresses or links.
email_idYesFrom the list of customer emails.
store_idYesThe store's store_id (not its name).

Output Schema

NameRequiredDescriptionDefault
noteNo
email_idYes
store_idYes
draft_statusYes
dashboard_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only flag it as non-read-only and non-destructive; the description adds substantial behavior the annotations do not carry: nothing is sent, the draft appears in the Customer emails page, latency of about a minute, a cap of 4 drafts per email, and that drafting is unbilled.

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?

Front-loaded with purpose, then constraints and prerequisites in short declarative clauses; nearly every sentence carries new information. The final prerequisites sentence is a bit dense with three conditions stacked together, but nothing is wasted.

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?

An output schema exists, so return values need not be explained; the description still covers safety (no send), latency, quota, billing, permissions and ownership. That is everything an agent needs to decide and call correctly.

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 coverage is 100% and the note parameter's constraints (max 500 chars, no long digit strings, emails or links) are already documented in the schema. The description only echoes that the note is optional and states what the reply should say, adding little beyond structured data.

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 opens with a specific verb and resource ('write a draft reply to one customer email') and names the grounding sources (catalogue, pages, order status), so the agent can distinguish it from send_customer_email_reply without inspecting schemas.

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?

'Sends nothing: the draft waits in the store's Customer emails page for the team' gives a clear context in which this is the right tool versus actually replying. It states prerequisites (conversations permission, AI assistant switch, store ownership) but never names the sibling that would send a draft explicitly.

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