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

finance-mcp-server

by Marcusdt-UX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Subscriptions & Recurring Charges

finance_list_subscriptions
Read-onlyIdempotent

Detect recurring subscriptions, memberships, and bills from transaction history. Identify price hikes by comparing current charges to previous baselines.

Instructions

Detect recurring charges (subscriptions, memberships, bills) from transaction history using merchant-key normalization and cadence analysis. Flags price hikes vs the prior baseline. Args: none (analyzes all history). Returns { totals: {monthly, annual, count, hikes}, subscriptions: [{label, category, cadence, lastAmount, monthlyCost, occurrences, lastDate, nextDate, daysUntilNext, priceHike?}] }.

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_list_subscriptions"
  }
}

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?

Annotations already declare read-only and idempotent. The description adds valuable behavioral context: merchant-key normalization, cadence analysis, price hike flagging, and full return structure. No contradiction with annotations.

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?

Extremely concise: two sentences plus a detailed return type snippet. No wasted words, front-loaded with key action.

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?

Fully complete for a no-parameter tool: describes what it does, how it works, and returns a detailed structure. No output schema, so the description carries the full burden, which it meets.

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 exist (0 params, 100% schema coverage). Baseline 4 is appropriate; the description explicitly states 'Args: none'.

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 detects and lists recurring charges from transaction history using specific analysis methods. It distinguishes itself from sibling tools like finance_search_transactions or finance_spending_by_category by focusing specifically on subscriptions and recurring charges.

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 explains it analyzes all history with no args, implying it's the go-to for subscriptions. It lacks explicit exclusions or comparisons to alternatives, but the purpose is clear given the sibling set.

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