Skip to main content
Glama
Sign In

Fresha MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List sales

list_sales
Read-onlyIdempotent

Sales (invoices) in a date range: number, date, client, status and totals. Lists sales as Sales > Sales list shows them for the days given, one row per sale with Fresha's columns (sale number, date, client, status, gross total and so on; linked records come with an _id). Amounts are in the business's currency. Page with next_cursor.

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": {
      "from": "<from>"
    },
    "name": "list_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day. Default: same as from.
fromYesFirst day.
limitNoPage size. Default: 50.
cursorNonext_cursor from the previous call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description usefully adds that amounts are in the business's currency, that linked records carry an `_id`, and that paging is via next_cursor. It stops short of stating rate limits or what an empty range returns, which keeps it from a 5.

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?

It is compact and front-loads the resource and scope, but the opening list of fields ('number, date, client, status and totals') is immediately restated as 'sale number, date, client, status, gross total and so on', which is redundant duplication rather than new information.

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 carries the burden of describing the return shape, and it does: one row per sale, the column set, `_id` on linked records, currency of amounts, and cursor-based paging. That covers what a four-parameter read tool needs, though the 'and so on' vagueness leaves the exact column list partly open.

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 every parameter (from, to, limit, cursor) is already documented in the schema, so the baseline of 3 applies. The description only reinforces the date-range semantics ('for the days given') and points at next_cursor for paging, adding little beyond the structured fields.

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 states a specific verb and resource ('Lists sales') plus the scope (a date range) and the columns returned. It is clearly distinguishable from the write-oriented siblings, but it never names get_sales_summary, the closest read alternative, leaving the agent to infer the split from the label alone.

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?

Usage is only implied: an agent can deduce 'use this to enumerate individual sales over a date window' from 'for the days given'. There is no explicit when-to-use, no exclusion, and no routing to get_sales_summary for aggregate numbers, which is a real ambiguity given that sibling exists.

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