Skip to main content
Glama

chase_transfers

Retrieve recent transfer history from your Chase accounts. Returns a list of transfers made.

Instructions

Get recent transfer history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:120-128 (registration)
    Tool 'chase_transfers' is registered in the ListToolsRequestSchema handler with name, description, and empty inputSchema (no parameters required).
    {
      name: "chase_transfers",
      description:
        "Get recent transfer history.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • The Transfer interface defines the schema for transfer objects returned by the tool: id, fromAccount, toAccount, amount, date, and status.
    export interface Transfer {
      id: string;
      fromAccount: string;
      toAccount: string;
      amount: number;
      date: string;
      status: "pending" | "completed" | "failed";
    }
  • The CallToolRequestSchema handler for 'chase_transfers' which calls getTransfers() and returns the result as JSON.
    case "chase_transfers": {
      const result = await getTransfers();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result),
          },
        ],
        isError: !result.success,
      };
    }
  • The getTransfers() function is the core implementation. It navigates to the Chase transfer page, scrapes transfer rows, and returns an array of Transfer objects (up to 20) with success/error status.
    export async function getTransfers(): Promise<{ success: boolean; transfers?: Transfer[]; error?: string }> {
      try {
        const p = await getPage();
        await p.goto(`${CHASE_BASE_URL}/web/auth/transfer`, { waitUntil: "networkidle" });
        
        await p.waitForTimeout(2000);
        
        const transfers = await p.$$eval(
          '.transfer-row, .activity-row, [data-testid="transfer"]',
          (elements) =>
            elements.slice(0, 20).map((el, index) => {
              const fromEl = el.querySelector('.from-account, .source');
              const toEl = el.querySelector('.to-account, .destination');
              const amountEl = el.querySelector('.amount');
              const dateEl = el.querySelector('.date, .transfer-date');
              const statusEl = el.querySelector('.status');
              
              const amountText = amountEl?.textContent?.trim() || '0';
              const amount = parseFloat(amountText.replace(/[$,]/g, '')) || 0;
              
              let status: 'pending' | 'completed' | 'failed' = 'completed';
              const statusText = statusEl?.textContent?.toLowerCase() || '';
              if (statusText.includes('pending')) status = 'pending';
              else if (statusText.includes('failed') || statusText.includes('cancelled')) status = 'failed';
              
              return {
                id: el.getAttribute('data-transfer-id') || `transfer-${index}`,
                fromAccount: fromEl?.textContent?.trim() || 'Unknown',
                toAccount: toEl?.textContent?.trim() || 'Unknown',
                amount,
                date: dateEl?.textContent?.trim() || '',
                status,
              };
            }),
        );
        
        return { success: true, transfers };
      } catch (error) {
        return {
          success: false,
          error: error instanceof Error ? error.message : "Failed to get transfers",
        };
      }
    }
Behavior1/5

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

With no annotations provided, the description must disclose behavioral traits. It fails to mention that this is a read-only operation, whether authentication is required, or if there are limitations like pagination or date ranges. The tool name implies a read operation but is not explicitly stated.

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

Conciseness3/5

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

The description is extremely concise (one sentence), but this brevity sacrifices important details. It is front-loaded with the core action but lacks any structure or additional context.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It does not explain what 'recent transfer history' entails (e.g., fields returned, time range), leaving the agent without enough context to use the tool confidently.

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?

There are zero parameters, so the input schema provides complete coverage. The description does not add meaning beyond the schema, but the baseline for no parameters is 4.

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 tool retrieves recent transfer history, which is a specific verb and resource. It distinguishes from sibling 'chase_transfer_preview' which likely handles previewing a new transfer, but does not explicitly differentiate.

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 is provided on when to use this tool versus alternatives like 'chase_transfer_preview' or 'chase_transactions'. The description gives no context about prerequisites or typical usage scenarios.

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