Skip to main content
Glama
Sign In

Fresha MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get sales summary

get_sales_summary
Read-onlyIdempotent

Sales summary for a period: sales, refunds, discounts, taxes and payments by type. Reads Reports > Sales summary for the days given: one row per sale type (services, products, memberships, gift cards and so on) with Fresha's own columns (gross and net sales, discounts, refunds, taxes) and a totals row. columns names each key. A period without sales has no rows. Amounts are in the business's currency.

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": "get_sales_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day. Default: same as from.
fromYesFirst day.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: one row per sale type plus a totals row, Fresha's fixed columns, amounts in the business's currency, and an empty period yielding zero rows. 'columns names each key' is cryptic and refers to something not present in the schema, which muddies rather than clarifies the return shape.

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 resource and contents, and most sentences carry real information (totals row, currency, empty-period behavior). The fragment 'columns names each key' is confusing and out of place given no columns parameter exists, which costs it a point.

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?

No output schema exists, so the description shoulders the return-shape burden and largely does so: row grain, column families, totals row, currency, and empty-result behavior. It falls short only on the ambiguous 'columns' reference and on not clarifying the relationship to list_sales.

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 both parameters already carry descriptions, including the 'Default: same as from' behavior for 'to'. The description only restates the period concept ('for the days given') without adding format, timezone, or range constraints beyond the schema.

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?

States a specific verb and resource ('Sales summary for a period') and enumerates the content (sales, refunds, discounts, taxes, payments by type), which clearly separates it from a raw-record tool like list_sales. It never names that sibling, so an agent must infer the distinction from the 'summary / one row per sale type / totals row' framing.

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 implied rather than stated: 'Reads Reports > Sales summary for the days given' tells the agent what it mirrors in the UI, and the period-scoped framing hints at reporting use cases. There is no explicit statement of when to prefer this over list_sales, nor any prerequisite or exclusion.

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