Skip to main content
Glama
Sign In
Fresha MCP Server

Fresha MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List sales

list_sales
Read-onlyIdempotent

Retrieve sales (invoices) for a specified date range, including number, date, client, status and totals, with cursor pagination.

Instructions

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 observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: amounts are in the business's currency, linked records carry an `_id`, and results are paginated. It stops short of saying how the date range is interpreted (inclusive boundaries, timezone) or what happens with very large ranges.

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 and reasonably tight: the shape of the rows comes first, then the pagination instruction. The two paragraphs partially restate each other (date range and column list appear twice), which costs a little economy but no clarity.

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 does the work of describing the return shape (columns, currency, `_id` on linked records) and pagination. That is enough to call the tool correctly, though the treatment of inclusive date boundaries and default range behavior is left to the schema alone.

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%, with defaults for `to` and `limit` documented inline, so the baseline is 3. The description only reinforces 'date range' and 'next_cursor', adding no format details or constraint semantics beyond what the schema already provides.

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 ('Sales (invoices) in a date range') and enumerates the columns returned (sale number, date, client, status, gross total). It does not explicitly distinguish itself from the sibling get_sales_summary, so a reader must infer list-vs-aggregate on their own.

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 by the date-range framing; there is no statement of when to call this versus get_sales_summary or how to handle open-ended ranges. The pagination hint ('Page with next_cursor') is the only actionable guidance.

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

Deploy Server

Other Tools