Skip to main content
Glama

Ventes en caisse

list_sales
Read-onlyIdempotent

Liste l'historique des ventes (filtres optionnels : période, client, méthode de paiement, statut). (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": "list_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLes N derniers jours, aujourd'hui compris (défaut : 30)
limitNoNombre maximum de ventes renvoyées (défaut 20).
statusNocompleted = ventes confirmées, cancelled = ventes annulées. Vide = toutes.
customer_idNoIdentifiant d'un client : seulement ses ventes. Vide = tous les clients.
payment_methodNoFiltrer par moyen de paiement (mobile_money = tous les portefeuilles mobiles)

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the trailing '(Lecture seule.)' merely restates structured data and earns no credit. Beyond that the description reveals only that all filters are optional; it says nothing about default window, result volume, or ordering behavior.

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 a single front-loaded sentence that names the resource first and the filters second, with no filler. The trailing '(Lecture seule.)' is redundant with the annotations and is the only wasted clause.

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?

For a read-only, zero-required-parameter list tool whose schema fully documents filtering and defaults, and whose annotations cover the safety profile, the description is sufficient to call it correctly. The only meaningful gap is that the default 30-day window and the 20-row cap are not surfaced in prose.

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%, so every parameter (days, limit, status, customer_id, payment_method) is already documented with defaults and enum meanings in the schema. The description's filter list (période, client, méthode de paiement, statut) maps onto the same fields without adding format or interaction detail, and omits 'limit' entirely, so baseline 3 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 states a concrete verb and resource ('Liste l'historique des ventes') plus the optional filter dimensions, so an agent knows it is a filtered list of sales records. It does not differentiate itself from nearby tools such as get_sales_report or list_sale_payments, so it stops short of a 5.

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: the parenthetical shows which filters exist, which suggests 'use this to browse/query sales history'. There is no statement about when to prefer this over get_sale, get_sales_report, or get_sales_full_analytics, and no exclusions or prerequisites.

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