Skip to main content
Glama
alex1092

Up Banking MCP Server

up_list_accounts

Retrieve and display all banking accounts for authenticated users, including balances, account types (SAVER, TRANSACTIONAL, HOME_LOAN), and ownership details. Filter results by account type or ownership type to organize financial information.

Instructions

List all accounts for the authenticated user. Returns account balances, types (SAVER, TRANSACTIONAL, HOME_LOAN), and ownership information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountTypeNoFilter by account type
ownershipTypeNoFilter by ownership type

Implementation Reference

  • The MCP tool handler for 'up_list_accounts' which parses arguments, calls UpApiClient.listAccounts, and returns the JSON-formatted result.
    case "up_list_accounts": {
      const args = request.params.arguments as {
        accountType?: "SAVER" | "TRANSACTIONAL" | "HOME_LOAN";
        ownershipType?: "INDIVIDUAL" | "JOINT";
      };
      const result = await client.listAccounts(args);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:227-246 (registration)
    Registration of the 'up_list_accounts' tool in the TOOLS array, including name, description, and input schema definition.
    {
      name: "up_list_accounts",
      description:
        "List all accounts for the authenticated user. Returns account balances, types (SAVER, TRANSACTIONAL, HOME_LOAN), and ownership information.",
      inputSchema: {
        type: "object",
        properties: {
          accountType: {
            type: "string",
            enum: ["SAVER", "TRANSACTIONAL", "HOME_LOAN"],
            description: "Filter by account type",
          },
          ownershipType: {
            type: "string",
            enum: ["INDIVIDUAL", "JOINT"],
            description: "Filter by ownership type",
          },
        },
      },
    },
  • Core implementation in UpApiClient for listing accounts: builds the API endpoint with optional filters and invokes the generic makeRequest method.
    async listAccounts(filters?: {
      accountType?: "SAVER" | "TRANSACTIONAL" | "HOME_LOAN";
      ownershipType?: "INDIVIDUAL" | "JOINT";
    }): Promise<{ data: AccountResource[] }> {
      let endpoint = "/accounts";
      const params = new URLSearchParams();
    
      if (filters?.accountType) {
        params.append("filter[accountType]", filters.accountType);
      }
      if (filters?.ownershipType) {
        params.append("filter[ownershipType]", filters.ownershipType);
      }
    
      if (params.toString()) {
        endpoint += `?${params.toString()}`;
      }
    
      return this.makeRequest(endpoint);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool returns balances, types, and ownership info, but lacks details on permissions required, rate limits, pagination, or error handling. For a list operation with no annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with zero waste: the first states the action and scope, and the second specifies return data. It's front-loaded with the core purpose and efficiently structured, making every sentence earn its place.

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?

Given no annotations and no output schema, the description provides basic purpose and return data but lacks completeness for a list tool. It doesn't cover response format details, error cases, or authentication context, which are important for agent usage. The schema handles parameters well, but overall context is minimally adequate.

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 both parameters ('accountType' and 'ownershipType') well-documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as default behaviors or interaction effects, so it meets the baseline for high schema coverage without extra value.

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 clearly states the verb ('List') and resource ('accounts for the authenticated user'), specifying what the tool does. It distinguishes from siblings like 'up_get_account' (singular retrieval) and 'up_get_transaction' (different resource), but doesn't explicitly contrast with 'up_list_categories' or 'up_list_transactions' which share the 'list' pattern for different resources.

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?

The description implies usage for viewing all accounts with optional filtering, but doesn't explicitly state when to use this vs. alternatives like 'up_get_account' for single accounts or 'up_list_transactions' for transaction data. No exclusions or prerequisites are mentioned, leaving usage context somewhat implied rather than clearly defined.

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/alex1092/up-bank-mcp-server'

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