Skip to main content
Glama

Chiffre d'affaires détaillé

get_sales_full_analytics
Read-onlyIdempotent

Analyse 360° du chiffre d'affaires sur N jours (ventes en caisse + factures définitives, comme le module Rapports ; détail caisse / factures inclus) : CA total, nb ventes, panier moyen, répartition par moyen de paiement (mobile money inclus), top 5 produits, flop 5 produits, top 5 clients, ventes par jour. Pour une vue d'ensemble complète. (Lecture seule.)

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

Input Schema

NameRequiredDescriptionDefault
daysNoPériode : les N derniers jours, aujourd'hui compris (défaut 30).

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 readOnlyHint, idempotentHint and destructiveHint=false, so the '(Lecture seule.)' tail adds nothing. The description does earn credit for disclosing the data scope: revenue is built from cash-register sales plus definitive invoices only ('factures définitives'), matching the Reports module, which tells the agent that draft invoices are excluded — a real behavioral trait not present in the annotations or schema.

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?

The purpose and the metric list are front-loaded in a single dense sentence, and every enumerated item corresponds to actual output content an agent would want to know. The closing '(Lecture seule.)' is redundant against the annotations and the trailing 'Pour une vue d'ensemble complète' is filler.

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 usefully enumerates the full return payload (totals, counts, payment-method split including mobile money, top/flop products, top customers, daily series) and explains the underlying data sources. Only minor gaps remain, such as currency or how top-5 ties are chosen, which are not critical for invocation.

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?

There is only one parameter and schema description coverage is 100%: the schema already states that 'days' is the last N days including today, defaulting to 30. The description adds nothing beyond 'sur N jours', so the baseline 3 for fully documented schemas applies.

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 opens with a specific verb-and-resource ('Analyse 360° du chiffre d'affaires') and then enumerates exactly what is returned (total revenue, sales count, average basket, payment-method split, top/flop products, top customers, daily sales). It clearly differentiates itself as the comprehensive aggregate view ('Pour une vue d'ensemble complète'), though it never names a sibling tool it is not.

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?

The phrase 'Pour une vue d'ensemble complète' implies the use case (want a full revenue overview), but there is no explicit when-not guidance and no named alternative such as get_revenue_by_payment_method, get_top_products, or get_sales_report for narrower questions. Usage is inferable but not routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources