Skip to main content
Glama
dfrysinger

finance-mcp

by dfrysinger

subscriptions_detect

Scans transaction history for recurring monthly charges, saves them as tracked bills, and flags unsupported cadences or subscriptions needing review.

Instructions

Detect recurring charges from history and save them as tracked bills.

Scans the archive for merchants with repeated, same-amount, monthly-spaced debits and writes each as a recurring bill in the budget config (creating the config if absent), so your subscriptions become a saved list rather than something re-inferred on every audit. Idempotent: a merchant already tracked is skipped. Dates are YYYY-MM-DD; end defaults to today and start to a year back. day_tolerance (default 7) is the day-of-month drift allowed when deciding whether a charge is already covered by an existing bill. Weekly/yearly merchants are reported under unsupported_cadence (only monthly bills are tracked). Monthly merchants that could not be auto-tracked — text too generic/variable to pin, or a recurring charge at a different price from an already-tracked subscription — are reported under needs_review (each with a reason) rather than written.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo
startNo
day_toleranceNo
min_occurrencesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. It discloses idempotency (skips already tracked merchants), mutation (writes to config, creates if missing), date formats, defaults, and cadence restrictions. It also explains edge cases like unsupported cadence and needs_review. Comprehensive coverage.

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?

Description is a single paragraph, front-loaded with the main action. It efficiently packs necessary details without excessive fluff. Minor redundancy ('so your subscriptions become a saved list...') but overall concise and well-structured.

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 4 parameters, no required ones, no annotations, and an output schema that exists but is not shown, the description covers core functionality, defaults, and edge cases. It mentions outputs (`unsupported_cadence`, `needs_review`) but lacks detail on output structure. Missing `min_occurrences` explanation slightly reduces completeness.

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 coverage is 0%, so description must add meaning. It explains `end`, `start`, and `day_tolerance` with defaults and format. However, it omits `min_occurrences` (default 3) entirely, leaving its role unclear. Thus partially compensates but has a clear gap.

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?

Description clearly states the tool detects recurring charges and saves them as tracked bills. It specifies the resource (history, merchants) and action (detect, save), distinguishing it from siblings like subscription_audit_report (likely read-only) and subscriptions_mark (likely manual).

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?

Description explains when to use the tool for automatic detection and saving of subscriptions. It clarifies that weekly/yearly merchants go to 'unsupported_cadence' and ambiguous ones to 'needs_review', providing context on limitations. However, it does not explicitly mention alternatives or when not to use it.

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