FreeScout MCP Server and API by Cotlet

Draft reply in FreeScout

freescout_draft_reply

Read-onlyIdempotent

Draft reply in the user's own FreeScout account from ChatGPT, Claude or any AI agent. Returns how to do it in FreeScout step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's FreeScout Cloud Browser. FreeScout's official API: FreeScout has a REST API, but only through its paid API & Webhooks module, and it has no official MCP server (checked 23 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "freescout_draft_reply"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description adds real context beyond the annotations: it opens nothing by itself, it returns procedural steps rather than performing an action, and it explains why browser automation is required (FreeScout has no official MCP server, and its REST API only ships in a paid module). That reconciles a tool named 'draft_reply' with readOnlyHint=true. It does not describe the shape or length of the returned steps.

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

Conciseness3/5

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

The core behavior and workflow are present, but padding dilutes them: 'from ChatGPT, Claude or any AI agent' adds nothing, and the API/MCP aside with a checked date is verbose. The critical 'opens nothing by itself' clause is buried mid-sentence rather than front-loaded.

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 zero-parameter, no-output-schema guide tool, it covers what is returned (screens, buttons, fields), what is not done (nothing opened), and what to do next (cotlet_browser_* calls). Only the format of the returned steps is left under-specified.

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?

The tool takes zero parameters, so the schema carries no semantics to supplement and the baseline is 4. The description correctly implies no inputs are needed.

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

Purpose3/5

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

The opening sentence ('Draft reply in the user's own FreeScout account from ChatGPT, Claude or any AI agent') reads as if the tool performs the draft, while the second sentence reveals it only returns step-by-step instructions for the user to follow. The actual function is stated, but the front-loaded framing is misleading about the verb, and no sibling (e.g. freescout_read_conversation) is named to sharpen the distinction.

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?

It gives an explicit two-step workflow: call this to get the screens/buttons/fields, then execute with cotlet_browser_* tools in the FreeScout Cloud Browser. It does not state when not to use it or which browser tool sequence to prefer, but the operative path is clear.

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

All FreeScout MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?