Skip to main content
Glama

Détail d'un compte bancaire

get_bank_account
Read-onlyIdempotent

Détails d'un compte (solde dans SAMA, compte comptable, 10 derniers mouvements saisis dans la Banque). (Lecture seule.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant du compte bancaire ou du portefeuille mobile money.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so '(Lecture seule.)' is largely redundant. The description does add real behavioral value beyond the annotations by disclosing what the payload contains (SAMA balance, accounting account, and a capped set of 10 recent movements), which matters since no output schema exists.

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?

One front-loaded sentence with the returned fields in a parenthetical, followed by a short safety note. The '(Lecture seule.)' clause duplicates the readOnlyHint annotation and is the only wasted text.

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 single-parameter read with no output schema, the description is nearly self-sufficient: it tells the agent what fields come back and that the operation is read-only. Minor gaps remain, such as behavior when the account id does not exist and the units/currency framing of the SAMA balance.

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% with a single required 'id' parameter already documented as a bank account or mobile money wallet identifier. The description adds no further meaning about the identifier or its accepted values, 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?

The description names a specific resource and verb-equivalent ('Détails d'un compte') and enumerates the contents returned: SAMA balance, accounting account, and the last 10 recorded movements. It implicitly contrasts with list_bank_accounts by being a single-account detail fetch, but does not name any sibling explicitly.

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?

Usage is only implied: the singular 'un compte' signals one-account lookup while 'list_bank_accounts' and 'list_bank_transactions' cover enumeration. There is no explicit when-to-use or when-not-to-use statement, and the '10 derniers mouvements' cap does not tell the agent to switch to list_bank_transactions for full history.

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