Skip to main content
Glama

Aurio Bank Statement

Analizar extracto bancario

analizar_extracto
Read-onlyIdempotent

Analiza el extracto bancario que el usuario ha SUBIDO como fichero (CSV, Excel XLSX/XLS, Norma 43, OFX o PDF con texto de su banca online): gasto e ingresos del periodo, en qué categorías se va el dinero, totales mes a mes y las suscripciones y recibos fijos que paga, con su coste al año. Úsala para “en qué se me va el dinero”, “analiza mi extracto del banco”, “qué suscripciones estoy pagando”, “cuánto gasto al mes”, “cuánto me cuestan al año las suscripciones”, “resúmeme este extracto”. Pasa el fichero adjunto en el parámetro file. IMPORTANTE: si el usuario PEGA movimientos como texto en el chat, NO los proceses ni los resumas tú: pídele que suba el fichero del extracto (así Aurio solo devuelve totales y no hace falta que pegues tus movimientos). Aurio analiza el fichero al momento y no lo guarda; solo devuelve totales (nunca movimientos, IBAN ni nombres de personas). No conecta con el banco ni mueve dinero. English: analyzes an uploaded bank statement file (CSV/Excel/OFX/Norma 43/text PDF) and returns spending by category, monthly totals and detected subscriptions with yearly cost; never process statement text pasted into the chat — ask for the file instead.

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": {
      "file": "<file>"
    },
    "name": "analizar_extracto"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesBank statement file uploaded by the user (CSV, XLSX/XLS, N43, OFX or text PDF).

Output Schema

NameRequiredDescriptionDefault
ctaYes
netYes
kindYes
notesYes
incomeYes
monthsYes
periodYes
privacyYes
currencyYes
expensesYes
recurringYes
disclaimerYes
topCategoriesYes
transactionCountYes
transactionsLabelYes
subscriptionsAnnualYes
recurringExpensesAnnualYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description adds real behavioral context: the file is analyzed in the moment and not stored, output is aggregates only (never movements, IBAN or names), and it does not connect to the bank or move money. It omits error/unsupported-format behavior and any limits on file size or row count.

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?

Front-loaded with what it does, then triggers, then the hard constraint (pasted text) and privacy guarantees — good ordering. It is somewhat long and the full English restatement largely duplicates the Spanish text, which costs a bit of density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description still names the returned aggregates, and it covers the one behavioral trap an agent would otherwise fall into (processing pasted statement text). For a single-file-input analysis tool, nothing an agent needs to call it correctly 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% and the nested file object already documents file_id, file_name, mime_type and download_url. The description only tells the agent to pass the attached file in `file` and restates the accepted formats, so it adds little beyond the schema — the baseline 3 for full coverage applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (analizar) and resource (extracto bancario subido como fichero), enumerates the accepted formats (CSV, XLSX/XLS, Norma 43, OFX, PDF con texto) and the concrete outputs (gasto/ingresos, categorías, totales mensuales, suscripciones con coste anual). An agent knows exactly what it gets back without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit trigger phrases ("en qué se me va el dinero", "qué suscripciones estoy pagando", "cuánto gasto al mes") and an explicit when-not rule: if the user pastes transactions as text, do not process them — ask for the file. The routing condition is stated rather than inferred.

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