Skip to main content
Glama

Tickets de caisse

get_sales_report
Read-onlyIdempotent

Tickets de caisse sur les N derniers jours, aujourd'hui compris : nombre de ventes confirmées et annulées, total et panier moyen de la caisse seule (sans les factures). (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_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLes N derniers jours, aujourd'hui compris

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 redundant '(Lecture seule.)' adds nothing. What does add value is the disclosure of what the report contains — confirmed vs cancelled sale counts, total and average basket — and the important exclusion of invoices, which materially affects interpretation of the numbers. With no output schema, this content-level disclosure carries real weight.

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?

One front-loaded sentence that states scope first and metrics second, with the exclusion in parentheses where it belongs. The trailing '(Lecture seule.)' is the only wasted wording, since it duplicates the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with full schema coverage and clear annotations, the description covers scope and content adequately. It is still ambiguous whether the totals and average basket are a single aggregate across the N days or a per-day breakdown, which matters for an agent interpreting results in the absence of an output schema.

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 the single 'days' parameter already carries the description 'Les N derniers jours, aujourd'hui compris', which the description merely repeats. No extra meaning is added — there is no hint about boundaries for small values, defaults, or how the window interacts with the aggregation.

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 names a specific resource (cash-register tickets) and states the exact scope and metrics returned: confirmed and cancelled sale counts, total and average basket over the last N days including today. The clause 'caisse seule (sans les factures)' narrows it against invoice-based report siblings, though it does not name any alternative explicitly.

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 by the scope statement — use this when you need cash-register sales figures over a recent window excluding invoices. There is no explicit when-to-use/when-not-to-use guidance and no named alternative such as get_full_report or get_sales_full_analytics, so routing between the many report siblings is left to inference.

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