Skip to main content
Glama
FreeScout MCP Server

FreeScout MCP Server

Create Draft Reply

freescout_create_draft_reply

Creates an editable draft reply in FreeScout for a ticket, letting you review and revise the response before it is sent.

Instructions

Create a draft reply in FreeScout that can be edited before sending

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": {
      "ticket": "<ticket>",
      "replyText": "<replyText>"
    },
    "name": "freescout_create_draft_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoOptional CC recipients. Omit to preserve existing recipients; pass [] to clear.
toNoOptional TO recipients. Omit to preserve existing recipients; pass [] to clear.
bccNoOptional BCC recipients. Omit to preserve existing recipients; pass [] to clear.
ticketYesTicket ID, ticket number, or FreeScout URL
userIdNoUser ID creating the draft (defaults to env setting)
replyTextYesThe draft reply content (generated by the LLM)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.2.0
    • changedInput schema / properties / bcc / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • changedInput schema / properties / cc / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • changedInput schema / properties / to / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed2 schema fields changedv3.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "draftId": {
      -      "type": "number"
      -    },
      -    "message": {
      -      "type": "string"
      -    },
      -    "success": {
      -      "type": "boolean"
      -    },
      -    "ticketId": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "success",
      -    "message",
      -    "ticketId",
      -    "draftId"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully clarifies that the write produces an editable draft rather than sending mail, but adds nothing about where the draft persists, visibility to other agents, or whether repeated calls create duplicates.

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?

A single front-loaded sentence with zero filler that states the action and its most decision-relevant property (editable, not sent).

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

Completeness3/5

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

With fully documented parameters and no output schema, the definition covers the essentials for invocation, but for a six-parameter write tool it omits any note on draft lifecycle or what a successful creation returns.

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 100%, so all six parameters, including the omit-vs-empty-array semantics for to/cc/bcc, are already documented in the schema. The description adds no parameter-level meaning beyond that, which is the baseline 3 case when the schema carries the burden.

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

Purpose4/5

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

The description pairs a specific verb (Create) with a specific resource (draft reply) and clarifies the outcome: an editable draft, not a sent message. This distinguishes it from a hypothetical send tool, though it does not explicitly contrast with siblings like freescout_add_note.

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?

'Can be edited before sending' implies the draft workflow is the point, hinting that an agent should use this when a reply needs review rather than immediate delivery. There is no explicit when-not guidance or named alternative, so usage must be inferred.

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