Skip to main content
Glama
popechia

ABANCA MCP Server

by popechia

get_bank_accounts

Retrieve bank account details and balances from ABANCA using secure OpenBanking API access to view financial information.

Instructions

Retrieves a list of bank accounts and their balances.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and handler implementation for the get_bank_accounts tool.
    private setupTools() {
      this.server.tool(
        "get_bank_accounts",
        "Retrieves a list of bank accounts and their balances.",
        {},
        async () => {
          await this.ensureAuthenticated();
          try {
            const accounts = await this.apiClient.getAccounts();
            return {
              content: [{ type: "text", text: JSON.stringify(accounts, null, 2) }]
            };
          } catch (error: any) {
            return {
              isError: true,
              content: [{ type: "text", text: `Error fetching accounts: ${error.message}` }]
            };
          }
Behavior3/5

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

With no annotations provided, the description carries the full burden of disclosure. It provides minimal behavioral context by mentioning 'balances' (indicating account-level financial data is returned), but lacks details on pagination, authentication requirements, rate limits, or the complete structure of the returned data.

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?

The single-sentence description is efficient at 9 words, front-loaded with the action ('Retrieves'), and contains no extraneous text. However, similar to the calibration example, it doesn't quite achieve a 5 as it could slightly improve by noting the unfiltered nature of the retrieval given the empty parameter schema.

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?

For a tool with zero parameters and no output schema, the description provides the minimum viable context by identifying the resource type and key returned attribute (balances). However, given the lack of structured output schema, it should ideally describe the return format (e.g., list of objects with account IDs and balances) to be considered complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Per the rubric, 0 parameters equals a baseline score of 4. The description appropriately does not attempt to invent parameter semantics, though it could have noted 'accepts no filters' or 'retrieves all accessible accounts' to clarify the empty schema behavior.

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 a specific verb ('Retrieves') and resource ('bank accounts'), and mentions 'balances' which distinguishes it from the sibling tool 'get_account_transactions' (accounts vs. transactions). However, it does not explicitly reference the sibling relationship or when to choose one over the other, which prevents a 5.

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?

The description states what the tool does but provides no guidance on when to use it versus alternatives, prerequisites (e.g., authentication), or exclusion criteria. The distinction from 'get_account_transactions' must be inferred from the resource names rather than explicit guidance.

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