Skip to main content
Glama
popechia

ABANCA MCP Server

by popechia

get_account_transactions

Retrieve transaction history for a specific bank account using its IBAN to view recent financial activity and monitor account movements.

Instructions

Retrieves the transactions for a specific bank account IBAN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ibanYesThe IBAN of the account to fetch transactions for
days_agoNoNumber of days of history to fetch (default: 30)

Implementation Reference

  • The handler function for 'get_account_transactions' which fetches transactions via apiClient.
    async ({ iban, days_ago }) => {
      await this.ensureAuthenticated();
      try {
        const accountId = await this.apiClient.resolveAccountId(iban);
        const transactions = await this.apiClient.getTransactions(accountId, days_ago || 30);
        return {
          content: [{ type: "text", text: JSON.stringify(transactions, null, 2) }]
        };
      } catch (error: any) {
        return {
          isError: true,
          content: [{ type: "text", text: `Error fetching transactions: ${error.message}` }]
        };
      }
    }
  • Registration of the 'get_account_transactions' tool, including its schema definition.
    this.server.tool(
      "get_account_transactions",
      "Retrieves the transactions for a specific bank account IBAN.",
      {
        iban: z.string().describe("The IBAN of the account to fetch transactions for"),
        days_ago: z.number().optional().describe("Number of days of history to fetch (default: 30)")
      },
      async ({ iban, days_ago }) => {
        await this.ensureAuthenticated();
        try {
          const accountId = await this.apiClient.resolveAccountId(iban);
          const transactions = await this.apiClient.getTransactions(accountId, days_ago || 30);
          return {
            content: [{ type: "text", text: JSON.stringify(transactions, null, 2) }]
          };
        } catch (error: any) {
          return {
            isError: true,
            content: [{ type: "text", text: `Error fetching transactions: ${error.message}` }]
          };
        }
      }
    );
Behavior2/5

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

No annotations provided, so description carries full burden. It discloses only the basic read operation ('Retrieves') but omits critical financial API behaviors: pagination limits, rate limiting, data freshness/real-time vs cached status, authentication requirements, or error handling for invalid IBANs.

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?

Single 9-word sentence is efficient and front-loaded (verb first). No redundancy or fluff. However, for a financial data tool handling sensitive transaction history, this brevity may be excessive minimalism that sacrifices necessary behavioral context.

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?

With 100% schema coverage and only 2 simple parameters (one optional), the description is minimally adequate for invocation. However, lacking output schema and annotations, and given this retrieves financial transaction data, the description is incomplete regarding data volume, format expectations, and result set boundaries.

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 both 'iban' and 'days_ago' fully documented in the schema. The description mentions IBAN generically but does not add param-specific semantics, syntax guidance, or usage notes beyond what the schema already provides. Baseline 3 appropriate for high schema coverage.

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 uses specific verb 'Retrieves' and resource 'transactions' with scope 'for a specific bank account IBAN'. However, it does not explicitly distinguish from sibling tool 'get_bank_accounts' (which likely lists accounts vs. this retrieving transaction history for a specific account).

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?

No guidance provided on when to use this tool versus alternatives, nor prerequisites (e.g., suggesting users may need 'get_bank_accounts' first to obtain valid IBANs). The description is purely functional with no contextual usage hints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/popechia/mcppsd2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server