Skip to main content
Glama
berthelius

Frihet MCP Server

Create Bank Categorization Rule

frihet_bank_rule_create

Create bank auto-categorization rules with AND conditions and actions like set category, add tag, or assign client to automatically categorize incoming transactions.

Instructions

Create a new bank auto-categorization rule. Rules apply automatically to matching incoming transactions. A rule has conditions (AND logic) and actions (assign category, tag, or client). Example: name='Mercadona groceries', condition description contains 'MERCADONA', action category='groceries'. / Crea una nueva regla de categorizacion automatica de transacciones bancarias. Las reglas aplican condiciones (logica AND) y acciones (categoria, etiqueta, cliente).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRule name for identification / Nombre de la regla
actionsYesActions to apply when rule matches / Acciones a aplicar cuando la regla se cumple
isActiveNoWhether the rule is active (default true) / Si la regla esta activa (por defecto true)
conditionsYesRule conditions (AND logic — all must match) / Condiciones (logica AND — todas deben cumplirse)
Behavior4/5

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

Descriptions detail AND logic for conditions and automatic application, adding context beyond annotations. No contradiction with annotations. However, does not disclose if rules affect existing transactions or potential conflicts.

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 concise with front-loaded key info. Bilingual is slightly longer but still efficient. Each sentence adds value.

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?

No output schema, description does not explain return value (e.g., rule ID) or mention immediate activation (isActive default). Could cover error scenarios or post-creation behavior.

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 100% with good descriptions; description adds an example but does not significantly enhance parameter understanding beyond schema.

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 verb ('Create') and resource ('bank auto-categorization rule'). It distinguishes from sibling tools like 'frihet_bank_rules_list' (list) and 'categorize_transaction' (manual categorization).

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 that rules apply automatically to matching transactions and includes an example, but does not explicitly contrast with manual categorization or exclude scenarios. Adequate but not explicit comparison.

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/berthelius/frihet-mcp'

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