Skip to main content
Glama

Factures d'avoir

list_credit_notes
Read-onlyIdempotent

Liste les factures d'avoir (numéro AV-…, date, client, facture d'origine, montant, statut émis ou annulé). Filtres facultatifs : invoice_id (avoirs d'une facture) ou query (numéro d'avoir ou de facture, client). (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_credit_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximum d'avoirs renvoyés (défaut 20).
queryNoNuméro d'avoir ou de facture, nom du client
invoice_idNoAvoirs d'une seule facture

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 and destructiveHint=false, and the description's '(Lecture seule.)' merely repeats that. Beyond annotations it adds the possible status values ('émis ou annulé'), which is genuinely useful, but says nothing about ordering, pagination behavior, or what happens when filters match nothing.

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?

A single front-loaded sentence with two compact parentheticals; the resource and its fields come first, filters second, safety note last. The redundant '(Lecture seule.)' is the only wasted token against annotations that already say the same.

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 no output schema, the description compensates well by listing the fields and statuses returned, and it covers the two meaningful filters for a three-parameter tool. Pagination and sort order are the remaining gaps for a list operation, but nothing essential for a correct call is missing.

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%, so all three parameters are already documented, and the description's filter explanation largely restates them. It does reinforce the dual use of query (credit-note or invoice number, or customer name), but omits limit entirely, so it adds little beyond the schema.

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 gives a specific verb and resource ('Liste les factures d'avoir') and even enumerates the returned fields (numéro AV-…, date, client, facture d'origine, montant, statut), so an agent knows exactly what this tool yields. It does not explicitly contrast itself with get_credit_note or the other list_* siblings, leaving differentiation to the name alone.

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?

It clarifies that all filters are optional and presents invoice_id and query as alternative filtering paths, which implies when each is useful. It never states when to choose this tool over get_credit_note (single record) or when no filter should be applied, so real alternative guidance is missing.

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