Skip to main content
Glama

Conecto Bookkeeping

Save a bank rule

books_save_bank_rule

A bank rule, like Xero's: which new bank lines it matches and how to book them, so lines that come every month (bank fees, rent, the phone bill) book themselves. when: conditions on the counterparty, description or reference (contains, equals, starts_with, ends_with; any case), all of them or any (match). Narrow it with direction (in, out), amount_min and amount_max (the line's size, no sign) and bank_account. Book to account with an optional tax split off, or split by percent across accounts (70% phone, 30% private), each part with its own tax. Rules are tried by position, lowest first; the first that matches is the line's first suggestion in books_bank_lines, and books_apply_bank_rules books every line a rule matches. Matched by name; only what you pass changes. Costs $0.001 per call; nothing if it fails.

Input Schema

NameRequiredDescriptionDefault
taxNoA tax by name (books_get lists them), e.g. "VAT 19%".
nameYesThe rule's name, e.g. "Bank fees".
whenNo
matchNoall
splitNo
accountNoAn account code from the chart, e.g. "6600".
new_nameNo
positionNo
trackingNoTracking options by category, e.g. {"Department": "Service"} (books_list_tracking).
directionNo
amount_maxNo
amount_minNo
descriptionNoThe memo of the entries it books. Default: the line's own text.
bank_accountNoOnly lines on this bank account (its code); "" for any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations, it discloses important behavior: rules are matched by name, only passed fields change, rule ordering by position controls first suggestion, and costs are incurred per call unless it fails. These are meaningful behavioral details not captured by readOnly/destructive annotations.

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 dense but front-loads the purpose and then proceeds through matching, scoping, booking, ordering, and cost. For a 14-parameter nested tool, the length is largely justified, though some sentences are packed and could be structured more cleanly.

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?

Given the tool's complexity, nested schema, and lack of output schema, the definition covers the critical matching, booking, ordering, and cost behavior. Minor gaps remain around rename semantics, tracking, and what a successful save returns.

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?

With only 43% schema description coverage, the description compensates well by explaining when conditions, match all/any, direction, unsigned amount limits, bank account scoping, splits by percent, and position ordering. It still leaves new_name, tracking, and the memo description lightly covered.

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 defines a bank rule precisely with examples and distinguishes its effect from sibling tools like books_bank_lines and books_apply_bank_rules. Although the verb is carried by the tool title, the resource and behavior are unambiguous.

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?

It explains how saved rules participate in matching and booking, and names related tools that consume rules. It does not explicitly state create-vs-update or when not to use this tool, but the operational context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources