Skip to main content
Glama

chase_rewards

Retrieve your Chase Ultimate Rewards points and cash back balance.

Instructions

Get Ultimate Rewards points and cash back balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:144-152 (registration)
    Registration of the chase_rewards tool in the ListToolsRequestSchema handler, defining the tool name, description, and empty input schema.
    {
      name: "chase_rewards",
      description:
        "Get Ultimate Rewards points and cash back balance.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Handler for the chase_rewards tool in the CallToolRequestSchema switch statement. It calls getRewards() and returns the result.
    case "chase_rewards": {
      const result = await getRewards();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result),
          },
        ],
        isError: !result.success,
      };
    }
  • The actual implementation of getRewards(), which uses Playwright/Patchright to scrape Ultimate Rewards points balance, cash back balance, and tier from the Chase dashboard page.
    export async function getRewards(): Promise<{ success: boolean; rewards?: RewardsInfo; error?: string }> {
      try {
        const p = await getPage();
        await p.goto(`${CHASE_BASE_URL}/web/auth/dashboard`, { waitUntil: "networkidle" });
        
        await p.waitForTimeout(2000);
        
        const rewards = await p.evaluate(() => {
          const pointsEl = document.querySelector('.points-balance, .ultimate-rewards, [data-testid="points"]');
          const cashBackEl = document.querySelector('.cash-back-balance, [data-testid="cashback"]');
          const tierEl = document.querySelector('.rewards-tier, .membership-level');
          
          const pointsText = pointsEl?.textContent?.trim() || '0';
          const cashBackText = cashBackEl?.textContent?.trim() || '0';
          
          return {
            pointsBalance: parseInt(pointsText.replace(/[^0-9]/g, '')) || 0,
            cashBackBalance: parseFloat(cashBackText.replace(/[$,]/g, '')) || 0,
            pendingRewards: 0,
            tier: tierEl?.textContent?.trim() || undefined,
          };
        });
        
        return { success: true, rewards };
      } catch (error) {
        return {
          success: false,
          error: error instanceof Error ? error.message : "Failed to get rewards",
        };
      }
    }
  • Type definition for RewardsInfo, the data structure returned by getRewards().
    export interface RewardsInfo {
      pointsBalance: number;
      cashBackBalance: number;
      pendingRewards: number;
      tier?: string;
    }
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It states what data is retrieved but does not disclose whether the values are current, available, or include pending items. There is no mention of authentication requirements or rate limits.

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?

A single sentence that front-loads the action and resource. No filler words, but could be slightly more informative without adding bulk.

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 parameters and no output schema, the description is fairly complete for a simple balance query, but it lacks context on whether the result includes total rewards across all accounts or a specific card, and does not mention if it returns separate values for points and cash back.

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?

With zero parameters and 100% schema coverage, the description adds value by specifying exactly what is fetched: points and cash back balance. This clarifies the data types beyond the empty input schema.

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 uses a specific verb 'Get' and clearly identifies the resource as 'Ultimate Rewards points and cash back balance'. It distinguishes itself from sibling tools like 'chase_balance' (likely for checking/savings) 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'chase_balance' or 'chase_accounts'. It does not mention any prerequisites or context, leaving the agent to deduce usage from the tool name alone.

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