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

finance-mcp-server

by Marcusdt-UX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove Category Rule

finance_remove_category_rule
DestructiveIdempotent

Remove a transaction category rule by providing its exact match string. The rule is deleted, but previously recategorized transactions retain their new category.

Instructions

Delete a category rule by its exact match string. Transactions it already recategorized keep their current category (rules don't store the original). Args: match. Returns whether a rule was removed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "match": "<match>"
    },
    "name": "finance_remove_category_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchYesThe exact match string of the rule to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate destructive and idempotent behavior. The description adds context: transactions already recategorized are not reverted, and it returns a boolean indicating removal. No contradictions 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?

Two sentences with no redundant information. The purpose is front-loaded, and every sentence provides essential details.

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?

Despite no output schema, the description explicitly states the return value. Side effects and parameter semantics are covered. The tool is simple and the description is fully adequate.

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?

The sole parameter 'match' is fully defined in the schema with description. The description only mentions 'Args: match' without adding new information, meeting the baseline for 100% 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 action ('Delete'), the resource ('category rule'), and the method ('by its exact match string'). It differentiates from sibling tools like 'add_category_rule' and 'list_category_rules' by specifying deletion and exact matching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for removing a rule by its match string but does not explicitly state when to use it versus alternatives. It mentions a side effect (transactions keep categories) but lacks guidance on 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.

Deploy Server

Other Tools