Skip to main content
Glama

Mouvements bancaires

list_bank_transactions
Read-onlyIdempotent

Liste les mouvements saisis dans la Banque (versements, retraits, transferts, frais…) avec un résumé chiffré exact sur la période. (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_bank_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPériode : les N derniers jours, aujourd'hui compris (défaut 30).
typeNoNature du mouvement : deposit (versement), withdrawal (retrait), virement_interne, remise_cheques, remise_cartes, frais, agios, interets, encaissement_client, autre_entree, autre_sortie, transfer_in, transfer_out. Vide = toutes.
limitNoNombre maximum de mouvements renvoyés (défaut 20) ; le résumé chiffré couvre toute la période.
bank_account_idNoIdentifiant d'un compte : seulement ses mouvements. Vide = tous les comptes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so '(Lecture seule.)' adds no credit. The one genuinely useful behavioral disclosure is that the numerical summary is computed over the whole period while the returned rows are capped — but that same fact is also stated in the limit parameter description, so the description's added value is modest.

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 well-formed sentence that front-loads the resource and its contents, followed by a short parenthetical. The parenthetical is largely redundant with the annotations, which is the only waste.

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?

All four parameters are optional and fully documented, and annotations cover the safety profile, so the basics are complete. However, with no output schema, the description should say more about what the 'résumé chiffré' contains and whether results are ordered or paginated beyond the limit.

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%, with defaults and the full enum of movement types documented inline, so the schema carries parameter meaning. The description only implies a period filter ('sur la période') and adds no syntax, timezone, or account-selection nuance beyond what the schema already states.

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 mouvements saisis dans la Banque') and enumerates the kinds of entries returned (versements, retraits, transferts, frais), so the agent knows exactly what data this returns. It does not name or contrast with any sibling such as list_bank_accounts or get_full_report, so routing still requires inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives for account-level versus transaction-level questions. The only contextual note is '(Lecture seule.)', which describes safety rather than usage selection.

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