finance-agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_linked_itemsA | List Plaid Items linked via the Plaid CLI (Trial/Production). Prefer this over any local connect DB. |
| get_balancesA | Fetch live balances for all linked Items using |
| get_transactionsA | Fetch transactions via Plaid CLI for a date range across all linked Items. |
| get_liabilitiesA | Fetch credit/loan liability details via |
| get_investmentsA | Fetch investment holdings via |
| summarize_cashflowA | Summarize inflow/outflow and category spend for a period using Plaid CLI data + local category rules. Use for monthly planning. |
| list_goalsA | List saved financial goals the agent should remember across chats. |
| upsert_goalC | Create or update a financial goal (debt payoff, savings target, etc.). |
| list_plan_notesA | List monthly planning notes saved from prior conversations. |
| add_plan_noteA | Save a planning note for a month so future chats keep context. |
| list_category_rulesA | List merchant substring → category rules used when summarizing cashflow. |
| add_category_ruleA | Add a categorization rule: if merchant/name contains match_text, assign category. |
| list_account_nicknamesA | List human-friendly nicknames for Plaid account_ids. |
| upsert_account_nicknameA | Save a nickname for an account_id (e.g. 'Chase checking', 'Amex BCE'). |
| setup_helpA | Explain how banking (Plaid CLI) and planning memory (this MCP) work together. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action: fetching data, summarizing cashflow, and managing goals, notes, rules, and nicknames are all clearly separated. No two tools appear to overlap in purpose, and the list/add/upsert/get pairs are well delineated.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_goals, add_plan_note, get_balances). The verbs vary (list, get, add, upsert, summarize, setup) but the pattern is uniform and predictable, with no mixed casing or style deviations.
With 15 tools, the server is well-scoped for a finance planning assistant. Each tool contributes to either data retrieval or memory management, and no redundant or unnecessary tools are present. The count falls comfortably within the ideal 3-15 range.
The set covers reading live financial data, summarizing cashflow, and managing goals, notes, rules, and nicknames, but lacks any delete/remove operations for these mutable resources. Users can add or update but not delete plan notes, category rules, or goals, creating potential dead ends and making the lifecycle incomplete.