Skip to main content
Glama

Encaissements par moyen de paiement

get_revenue_by_payment_method
Read-onlyIdempotent

Répartition du chiffre d'affaires (caisse + factures définitives) par moyen de paiement sur N jours. (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_revenue_by_payment_method"
  }
}

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the parenthetical '(Lecture seule.)' adds nothing beyond them. The description does add meaningful scope information: revenue counts cash-register entries and finalised invoices only, which implies that drafts and other documents are excluded. It says nothing about the return shape, whether zero-value methods appear, or rounding/currency handling.

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?

Two short sentences with the scope statement front-loaded and no filler. The read-only parenthetical is slightly redundant with the annotations but costs little.

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 one-parameter, non-destructive reporting tool with full schema coverage and no output schema, the definition supplies the essential scope. An agent could call it correctly from this description alone, with only the response structure left implicit.

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%, and the single 'days' parameter is fully documented, including its default and an inclusive-of-today definition. The description's 'sur N jours' merely restates the schema, so the 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?

States a specific verb-and-resource pairing: a revenue breakdown by payment method, with the scope defined as cash-register takings plus finalised invoices over N days. That is clearly separable from siblings such as get_mobile_money_stats or get_sales_report, though it does not name those alternatives.

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 scope phrase '(caisse + factures définitives)' implicitly indicates when the tool applies, namely reporting takings by tender type. However, there is no explicit guidance on when to prefer or avoid it relative to other reporting tools, and there are no stated 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