Skip to main content
Glama
Sign In

Fresha MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get sales summary in Fresha

fresha_get_sales_summary
Read-onlyIdempotent

Get sales summary in the user's own Fresha account from ChatGPT, Claude or any AI agent. Returns how to do it in Fresha step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fresha Cloud Browser. Fresha's official API: Fresha has no public API and no developer docs (checked 11 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": "fresha_get_sales_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description still adds real value by stating 'opens nothing by itself' and noting Fresha has no public API or developer docs, which explains why a browser-based flow is required.

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 step-by-step return behavior is front-loaded in the second sentence, but the opening line ('from ChatGPT, Claude or any AI agent') is marketing filler and the '(checked 11 Oct 2026)' date adds noise without changing how the agent calls the tool.

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?

There is no output schema, so the description carries the burden of return-value disclosure, and it does state the shape of the response (step-by-step screens, buttons, fields). It could say more about how detailed or long that guidance is, but nothing essential for correct invocation is missing.

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 baseline applies; the description correctly signals that no arguments are needed and that the Fresha account context comes from the user's own session rather than from inputs.

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 second sentence is specific: the tool returns step-by-step instructions (screens, buttons, fields) and performs no browser action. But the leading sentence, 'Get sales summary in the user's own Fresha account', implies the tool retrieves data, which it explicitly does not, so an agent skimming only the first line could misjudge what it gets back.

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 names the follow-up path explicitly: use the cotlet_browser_* tools in the user's Fresha Cloud Browser after this guidance. The only gap is the absence of an explicit when-not statement or a named alternative for getting the summary some other way.

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