Skip to main content
Glama
dfrysinger

finance-mcp

by dfrysinger

subscriptions_mark

Mark a recurring bill as canceling, canceled, or active. Specify effective cancellation date and optionally flag the bill as variable for amount-flexible matching.

Instructions

Mark a tracked recurring bill as canceling, canceled, or active again.

The cancellation watch: after you cancel (or try to cancel) a subscription, record it here so the audit stops reporting its expected charges as missing and instead warns you if it charges again. lifecycle is canceling (a cancellation was attempted but not confirmed), canceled (confirmed), or active (reactivate a bill you'd marked). cancel_effective is the YYYY-MM-DD date the cancellation takes effect and is required for canceling and canceled — any matching charge on or after it is surfaced as the bill "coming back". Omit it when reactivating. variable optionally flags the bill as one whose amount changes every cycle (a usage-based or escrow bill): true matches it by merchant and date regardless of amount and reports the actual charged amount, false restores exact-amount matching, null leaves the setting unchanged. The bill is found by name (case-insensitive); the name must match exactly one bill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
variableNo
lifecycleYes
cancel_effectiveNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description thoroughly explains the consequences of marking lifecycle (audit behavior changes) and the effect of the variable flag on matching. It lacks mention of error handling, idempotency, or permissions, but given no annotations, it provides substantial transparency.

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 the main action first, then detailed explanations for each parameter. It avoids unnecessary details but could be streamlined slightly. Overall efficient.

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?

The description covers the main functionality, parameter details, and effects on audit. With an output schema present, it doesn't need to detail return values. It lacks mention of potential errors (e.g., if name doesn't match exactly one), but overall is contextually adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds complete semantics for all four parameters: explains valid values for lifecycle, format and conditional requirement for cancel_effective, and three-way behavior for variable. This fully compensates for the 0% schema coverage.

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's action (mark lifecycle status) and differentiates from sibling tools like subscriptions_detect and subscription_audit_report by focusing on lifecycle management. It uses specific verb 'mark' and specifies the resource and possible states.

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 details when to use each lifecycle state (canceling, canceled, active) and provides context for cancel_effective and variable. It lacks explicit mention of when not to use or alternative tools, but the context is sufficient for usage decisions.

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