Skip to main content
Glama
dfrysinger

finance-mcp

by dfrysinger

spending_summary

Aggregate net spending over a date range, grouped by category, account, month, or envelope. Excludes transfers and income by default to reflect real spending.

Instructions

Aggregate net spending over a date range, grouped for budgeting.

group_by is category (default), account, org, month, or envelope. Categories come from a local rules engine plus manual overrides. Internal transfers and income (payroll, benefits, investment income) are excluded by default so the totals reflect real spending; set exclude_transfers=False or exclude_income=False to include them.

Per group, outflow is spend, inflow is refunds/returns that net against it, and unclassified_inflow is positive amounts with no spending category (surfaced but not netted). net is outflow plus refunds.

envelope rolls spend up by the configured budget envelope that owns each account (so spend on a non-envelope account such as a loan or brokerage falls into an (unmapped) bucket). It needs at least one envelope in the budget config; with none configured it returns an error rather than an empty view.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNo
group_byNocategory
start_dateNo
exclude_incomeNo
include_pendingNo
exclude_transfersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full burden. It discloses exclusions of transfers/income by default, explains net calculation, and covers edge cases like unmapped envelopes and errors. Minor omission: no mention of rate limits or permissions.

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?

The description is well-structured with purpose first, then parameter details. Every sentence adds value, though slightly verbose in places. Front-loads key information effectively.

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

Completeness4/5

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

Given 6 parameters, no required, and output schema exists, the description covers group_by nuances and output fields. Missing details on date range defaults and include_pending behavior, but overall sufficient for agent understanding.

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?

Schema coverage is 0%, so description compensates well. It fully explains group_by options and output semantics (outflow, inflow, net, unclassified_inflow). It does not detail date or boolean parameters but schema provides defaults.

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 clearly states the tool aggregates net spending over a date range for budgeting, with a specific verb and resource. It distinguishes from siblings like get_transactions and account_balances.

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?

The description implies usage for budgeting by date range with grouping, and through sibling context suggests when to use alternatives. It lacks explicit when-not-to-use statements but provides clear context.

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/dfrysinger/finance-mcp'

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