Skip to main content
Glama
Sign In

Fresha MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Reply to review

reply_to_review
Destructive

Post a public reply to a client's review. Posts a reply under the review as Reply in Online reputation does, signed as the business or the team member. The reply is public on the business's Fresha page and the client is told, so this reaches people. It needs a review that exists: take review_id from list_reviews. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.

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": {
      "review_id": "<review_id>",
      "text": "<text>"
    },
    "name": "reply_to_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesReply text.
reply_asNoSign the reply as the business (default) or as the team member signed in.
review_idYesReview id from list_reviews.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the reply is public on the business page, that the client is notified, and that each call is confirmed by default and gated on owner approval. What it omits is the counterpart of destructiveHint=true: whether a posted reply can be edited or removed once published.

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 the action and the reach consequence, then prerequisites, then approval behavior — a sensible order. A few clauses are redundant ('posts a reply under the review as Reply in Online reputation' versus 'the reply is public') and could be trimmed.

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?

With no output schema, the description would need to hint at outcomes, and it does communicating the public visibility and client notification. Prerequisite sourcing and the approval gate are present; only the reversibility/editability question and any response payload remain unaddressed.

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 schema already explains review_id's origin and reply_as's enum meaning. The description's mention of signing 'as the business or the team member' only restates the same information; it adds no new syntax, format, or constraint detail.

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+resource — 'Post a public reply to a client's review' — plus the visible surface ('public on the business's Fresha page'). It also names list_reviews as the source of review_id, so it is clearly separable from that 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 a concrete prerequisite (the review must exist; get review_id from list_reviews) and discloses the confirmation/approval gate. It stops short of naming when NOT to reply or any alternative path for responding to a review privately.

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

All Fresha MCP Server and API by Cotlet toolsInspect
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