Skip to main content
Glama
henfrydls

actual-budget-mcp

by henfrydls

create_rule

Create a rule that automatically applies an action (set category, payee, or notes) when a transaction matches conditions on payee, category, or amount.

Instructions

Create a transaction rule. When a transaction matches the condition, the action is applied automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
condition_fieldYesField to match: payee, category, amount, notes, imported_payee
condition_opYesOperator: is, contains, oneOf, isNot, doesNotContain, matches, gt, lt, gte, lte
condition_valueYesValue to match against
action_fieldYesField to set: category, payee, notes
action_valueYesValue to set (category name/ID, payee name, or note text)
stageNoWhen to apply: null (default), pre, or postnull
Behavior2/5

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

Annotations already indicate readOnlyHint=false, so the description aligns with a write operation. However, it does not disclose additional behaviors such as potential limits, overwrite behavior, or side effects on existing rules.

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 concise sentences front-load the purpose and add context. No wasted words or redundant information.

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

Completeness3/5

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

Description covers the core concept but lacks details on return values or error scenarios. Without an output schema, the description could have added that information. However, for a simple creation tool, it is 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?

Schema description coverage is 100%, so the schema already documents all parameters. The tool description adds no extra meaning beyond what the schema provides, resulting in baseline score.

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 'Create a transaction rule' with verb and resource. It also explains the automatic behavior when conditions match, distinguishing it from sibling tools like delete_rule or get_rules.

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?

Description implies when to use (for automating actions on transactions) but does not explicitly exclude alternatives or provide comparisons to sibling tools like create_category or update_transaction. No 'when not to use' guidance.

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/henfrydls/actual-budget-mcp'

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