Skip to main content
Glama

chase_accounts

Retrieves all Chase bank accounts including checking, savings, credit cards, investments, and loans for balance viewing and financial management.

Instructions

Get all Chase accounts - checking, savings, credit cards, investments, and loans.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:69-76 (registration)
    Tool registration in the tool list (ListToolsRequestSchema handler): defines the 'chase_accounts' tool name, description, and empty input schema.
      name: "chase_accounts",
      description:
        "Get all Chase accounts - checking, savings, credit cards, investments, and loans.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Handler for the 'chase_accounts' tool in the CallToolRequestSchema switch statement. Delegates to getAccounts() from browser.ts and returns the result as JSON.
    case "chase_accounts": {
      const result = await getAccounts();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result),
          },
        ],
        isError: !result.success,
      };
    }
  • The actual implementation of the account-fetching logic. Uses Patchright to navigate to the Chase dashboard, scrape account tiles (name, balance, type, last-four digits), and return them as Account objects.
    export async function getAccounts(): Promise<{ success: boolean; accounts?: Account[]; error?: string }> {
      try {
        const p = await getPage();
        await p.goto(`${CHASE_BASE_URL}/web/auth/dashboard`, { waitUntil: "networkidle" });
        
        await p.waitForTimeout(2000);
        
        const accounts = await p.$$eval(
          '.account-tile, .account-card, [data-testid="account-tile"]',
          (elements) =>
            elements.map((el, index) => {
              const nameEl = el.querySelector('.account-name, .tile-header, h3');
              const balanceEl = el.querySelector('.account-balance, .balance, [data-testid="balance"]');
              const lastFourEl = el.querySelector('.account-last-four, .masked-number');
              const typeEl = el.querySelector('.account-type');
              
              const name = nameEl?.textContent?.trim() || `Account ${index + 1}`;
              const balanceText = balanceEl?.textContent?.trim() || '0';
              const balance = parseFloat(balanceText.replace(/[$,]/g, '')) || 0;
              const lastFour = lastFourEl?.textContent?.trim().replace(/[^0-9]/g, '').slice(-4) || undefined;
              
              let type: 'checking' | 'savings' | 'credit' | 'investment' | 'loan' = 'checking';
              const typeText = (typeEl?.textContent || name).toLowerCase();
              if (typeText.includes('saving')) type = 'savings';
              else if (typeText.includes('credit') || typeText.includes('card')) type = 'credit';
              else if (typeText.includes('invest') || typeText.includes('brokerage')) type = 'investment';
              else if (typeText.includes('loan') || typeText.includes('mortgage') || typeText.includes('auto')) type = 'loan';
              
              return {
                id: el.getAttribute('data-account-id') || `account-${index}`,
                name,
                type,
                balance,
                lastFour,
              };
            }),
        );
        
        return { success: true, accounts };
      } catch (error) {
        return {
          success: false,
          error: error instanceof Error ? error.message : "Failed to get accounts",
        };
      }
    }
  • Type definition for the Account interface, which defines the structure returned by getAccounts().
    export interface Account {
      id: string;
      name: string;
      type: "checking" | "savings" | "credit" | "investment" | "loan";
      balance: number;
      availableBalance?: number;
      accountNumber?: string;
      lastFour?: string;
    }
Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states 'Get' without clarifying authentication requirements, rate limits, or whether the response includes sensitive data. Minimal behavioral context beyond the obvious.

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 a single, front-loaded sentence with no wasted words. It efficiently communicates the tool's purpose.

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?

Without an output schema, the description could state what information is returned for each account (e.g., account IDs, balances). It is minimally complete for a list operation, but lacks details about the response format.

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?

The input schema has zero parameters and is fully covered by description (no need to describe params). Baseline for 0 parameters is 4, and the description does not add irrelevant information.

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?

The description clearly states the verb 'Get' and the resource 'all Chase accounts', listing specific account types (checking, savings, credit cards, investments, loans). This distinguishes it effectively from sibling tools like chase_balance and chase_transactions.

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 the tool is for listing all accounts, but it does not provide explicit guidance on when to use it versus siblings nor any exclusions or prerequisites.

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/markswendsen-code/mcp-chase'

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