Skip to main content
Glama
Sign In
finance-mcp-server

finance-mcp-server

by Marcusdt-UX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Real-Time Balances

finance_balances
Idempotent

Retrieve live per-account balances and net worth from linked bank accounts. Shows assets, liabilities, and net worth with credit card and loan balances as positive owed amounts.

Instructions

Live per-account balances and net worth via SimpleFIN (fetched fresh on each call, then cached). Credit-card and loan balances are shown as positive amounts OWED and subtracted from net worth. If the live fetch fails, returns the last cached balances with a note. Requires finance_link_bank first. No args. Returns { accounts: [{name, institution, type, balance, currency, as_of}], assets, liabilities, net_worth, live }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "finance_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Discloses key behaviors: fresh fetch per call with caching, sign convention for credit/loan balances, fallback to cached data with note. No annotation contradictions.

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?

Two sentences covering purpose, source, caching, sign convention, error handling, and return structure. No wasted words.

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

Completeness5/5

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

Given zero parameters, no output schema, the description provides a detailed return structure and error handling. Fully adequate for an agent to use correctly.

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?

No parameters; description explicitly notes 'No args.' Schema coverage is 100%, so description adds value by confirming no input needed.

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?

Clearly states it returns live per-account balances and net worth via SimpleFIN. Differentiates from sibling tools by specifying real-time nature and caching behavior. No ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

States prerequisite (requires finance_link_bank first) and fallback behavior when live fetch fails. Could explicitly mention when not to use among siblings, but overall clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools