Skip to main content
Glama
whitebirchio

Monarch Money MCP Server

by whitebirchio

get_account_balance

Retrieve the current balance for a specific financial account by providing the account ID, enabling users to check their account status within Monarch Money.

Instructions

Get the current balance for a specific account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesThe ID of the account

Implementation Reference

  • The actual implementation of getAccountBalance that retrieves account details including current balance, account name, type, and institution from the Monarch Money API
    private async getAccountBalance(accountId: string): Promise<any> {
      try {
        const accounts = await this.api.getAccounts();
        const account = accounts?.find((acc: Account) => acc.id === accountId);
    
        if (!account) {
          throw new Error(`Account with ID ${accountId} not found`);
        }
    
        return {
          success: true,
          data: {
            accountId: account.id,
            accountName: account.displayName,
            currentBalance: account.currentBalance,
            accountType: account.type?.name,
            institutionName: account.institution?.name,
          },
        };
      } catch (error) {
        throw new Error(
          `Failed to get account balance: ${
            error instanceof Error ? error.message : 'Unknown error'
          }`
        );
      }
    }
  • Tool definition with schema registration - defines the tool name, description, and input validation (requires accountId as a string)
    {
      name: 'get_account_balance',
      description: 'Get the current balance for a specific account',
      inputSchema: {
        type: 'object',
        properties: {
          accountId: {
            type: 'string',
            description: 'The ID of the account',
          },
        },
        required: ['accountId'],
      },
    },
  • src/tools.ts:209-210 (registration)
    Tool routing registration that maps the 'get_account_balance' tool name to its handler method
    case 'get_account_balance':
      return await this.getAccountBalance(args.accountId);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but doesn't mention permissions needed, rate limits, whether the data is real-time or cached, or what happens on errors. For a read operation with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 doesn't explain what the return value looks like (e.g., numeric balance, currency, timestamp) or address potential complexities like error handling. For a tool with no structured support, more context is needed.

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 the parameter 'accountId' fully documented in the schema. The description doesn't add any meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline score when the schema does the heavy lifting.

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 'Get' and the resource 'current balance for a specific account', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_accounts' or 'get_account_snapshots', which might also provide balance-related information, so it doesn't reach the highest score.

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. With siblings like 'get_accounts' and 'get_account_snapshots' that might offer similar or overlapping functionality, there's no indication of when this specific balance retrieval is preferred, leaving usage unclear.

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/whitebirchio/monarch-mcp'

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