Skip to main content
Glama
whitebirchio

Monarch Money MCP Server

by whitebirchio

get_net_worth

Retrieve current net worth with detailed breakdown of assets and liabilities from Monarch Money financial data.

Instructions

Get current net worth and assets/liabilities breakdown

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function getNetWorth() that implements the tool logic. It fetches accounts, categorizes them as assets or liabilities based on account type group, calculates totals and net worth, and returns a detailed breakdown with account lists.
    private async getNetWorth(): Promise<any> {
      try {
        const accounts = await this.api.getAccounts();
    
        let totalAssets = 0;
        let totalLiabilities = 0;
    
        const assetAccounts: any[] = [];
        const liabilityAccounts: any[] = [];
    
        accounts?.forEach((account: Account) => {
          if (!account.includeInNetWorth) {
            return; // Skip accounts not included in net worth
          }
    
          const balance = account.currentBalance || 0;
          const accountGroup = account.type?.group?.toLowerCase() || '';
    
          if (accountGroup === 'asset') {
            totalAssets += balance;
            assetAccounts.push({
              name: account.displayName,
              type: account.type?.name,
              balance: balance,
            });
          } else if (accountGroup === 'liability') {
            totalLiabilities += Math.abs(balance);
            liabilityAccounts.push({
              name: account.displayName,
              type: account.type?.name,
              balance: balance,
            });
          }
        });
    
        const netWorth = totalAssets - totalLiabilities;
    
        return {
          success: true,
          data: {
            netWorth,
            totalAssets,
            totalLiabilities,
            assetAccounts,
            liabilityAccounts,
          },
          summary: `Net worth: $${netWorth.toFixed(
            2
          )} (Assets: $${totalAssets.toFixed(
            2
          )}, Liabilities: $${totalLiabilities.toFixed(2)})`,
        };
      } catch (error) {
        throw new Error(
          `Failed to get net worth: ${
            error instanceof Error ? error.message : 'Unknown error'
          }`
        );
      }
    }
  • Tool registration schema defining get_net_worth with its description and input schema (empty object with no required parameters).
    {
      name: 'get_net_worth',
      description: 'Get current net worth and assets/liabilities breakdown',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • src/tools.ts:224-225 (registration)
    Case statement in executeTool() method that routes the 'get_net_worth' tool name to the getNetWorth() handler method.
    case 'get_net_worth':
      return await this.getNetWorth();
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 but offers minimal information. It states what the tool returns (net worth and breakdown) but doesn't describe whether this requires authentication, has rate limits, provides real-time vs. cached data, includes historical trends, or handles errors. For a financial data tool with zero 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 perfectly concise at 8 words in a single sentence that front-loads the core functionality. Every word earns its place: 'Get' establishes the action, 'current' specifies timing, 'net worth' identifies the primary metric, and 'assets/liabilities breakdown' adds crucial detail about the return structure. There is zero redundancy or wasted verbiage.

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 the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally complete. It tells the agent what the tool returns but doesn't provide enough context about the return format, data freshness, or relationship to sibling tools. For a net worth calculation tool among 10 financial siblings, more guidance would be helpful, but the description meets basic requirements for such a straightforward tool.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the input requirements. The description appropriately doesn't waste space discussing nonexistent parameters. It focuses on the output semantics (net worth and breakdown) which is valuable context given the lack of output schema.

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's purpose with a specific verb ('Get') and resource ('current net worth and assets/liabilities breakdown'), making it immediately understandable. It distinguishes itself from siblings like 'get_account_balance' or 'get_portfolio' by focusing on comprehensive net worth calculation rather than specific account balances or investment portfolios. However, it doesn't explicitly contrast with all siblings, leaving some ambiguity about when to choose this over other financial summary tools.

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 the 10 sibling tools. It doesn't mention alternatives like 'get_monthly_summary' or 'get_budget_summary', nor does it specify prerequisites, timing considerations, or use case scenarios. The agent must infer usage context solely from the tool name and description without explicit direction.

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