Skip to main content
Glama

Dépenses

list_expenses
Read-onlyIdempotent

Liste les dépenses avec un résumé chiffré exact (total, nombre) sur la période. La paie et le personnel sont exclus de ce serveur par conception, et aucun réglage ni aucun droit ne les ouvre : aucun outil ne donne accès aux salaires, aux bulletins de paie ni aux salariés, et aucun ne peut en établir ; ils se consultent seulement dans SAMA Entreprise. (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_expenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPériode : les N derniers jours, aujourd'hui compris (défaut 30).
limitNoNombre maximum de dépenses renvoyées (défaut 20) ; le résumé chiffré couvre toute la période.
categoryNoCatégorie exacte de la dépense, telle qu'elle figure sur les dépenses. Vide = toutes.

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 '(Lecture seule.)' note merely repeats structured data. The genuinely additive context is the hard architectural exclusion of payroll/personnel data and the guarantee that the numeric summary holds even when the result list is truncated; nothing about rate limits, ordering, or response shape is added.

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 core capability is front-loaded in one clean sentence with zero waste. The second sentence is longer than needed for the exclusion rule and closes with a parenthetical that duplicates the readOnly annotation, so there is minor redundancy but no confusion.

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 three optional parameters, no output schema, and annotations covering the safety profile, the description is nearly sufficient: it states the return content (total and count) and the period semantics. It omits any mention of default ordering or how the summary interacts with the category filter, which would round it out.

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 the baseline is 3; all three parameters (days, limit, category) are already documented at field level. The description's statement that the summary spans the whole period mirrors what the schema already says for 'limit', so it adds little new meaning.

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 first sentence states a specific verb and resource (list expenses) plus a distinguishing trait: a 'résumé chiffré exact (total, nombre)' over a period, which separates it from a plain listing or a get_expense lookup. It does not name a sibling tool to differentiate against, which keeps it just 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?

The description spends most of its guidance budget on what the tool cannot do (payroll/personnel, no permission unlocks it, consult SAMA Entreprise instead), which is useful negative guidance. However, it never says when to prefer this over get_expense or how it relates to the other list_* endpoints, so positive selection guidance is only implied.

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