Skip to main content
Glama

Factures et devis

list_invoices
Read-onlyIdempotent

Liste factures/devis avec filtres. Aucun outil de ce serveur ne change le statut d'un document (marquer une facture payée, l'émettre, l'envoyer, l'annuler) ni n'enregistre de paiement : ces actions se font seulement dans SAMA Entreprise, par un utilisateur autorisé. (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_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoquote = devis, proforma = proforma, definitive = facture, acompte = facture d'acompte. Vide = tous.
limitNoNombre maximum de documents renvoyés (défaut 10).
statusNodraft = brouillon, sent = émise, paid = payée, overdue = en retard, cancelled = annulée. Vide = tous.
customer_idNoIdentifiant d'un client : seulement ses documents. Vide = tous les clients.

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, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description reinforces read-only and usefully points to where mutations actually occur (SAMA Entreprise, authorized user), but that is largely a restatement of the annotation plus an external pointer; it adds no detail on result shape, ordering, or pagination behavior beyond the 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?

Short and front-loaded: the capability comes first, the boundary second. The trailing '(Lecture seule.)' and the closing caveat repeat what the first clause and the readOnlyHint annotation already establish, so a small amount of wording does not earn its place.

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?

This is a low-complexity read-only list with four optional, fully documented parameters and rich annotations, and the description covers both capability and the mutation boundary. The only gap is that with no output schema it does not indicate what a returned document record looks like or how results are ordered — minor for a list tool.

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 both enums are fully glossed in the schema (quote/devis, definitive/facture, draft/brouillon, etc.), so the description owes no compensation. 'Avec filtres' only signals that filtering exists without adding meaning to limit, status, type or customer_id, so the baseline of 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 opens with a clear verb+resource statement ('Liste factures/devis avec filtres'), which is specific enough to distinguish this from get_overdue_invoices or get_invoice by name alone. However, it does not explicitly state the scope difference (all statuses/types vs. overdue-only) that would make the sibling distinction unambiguous.

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 rules out a whole class of uses (no status changes, no payment recording, those happen in SAMA Entreprise), which is real guidance. It says nothing about when to prefer this tool over get_overdue_invoices or the single-document get_invoice, leaving the main routing decision to inference from names.

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