Skip to main content
Glama

save_account_lines

Saves an account's income and expense category lines for a closed month, allocating its pre-set totals without changing them; use only before the first open month.

Instructions

Saves an account's lines by category (income and expense) for a CLOSED month before the first open month of the wizard queue: what that month's account totals were made of. For the first open month use preview_statement / commit_statement; this tool refuses that month and later ones with 409 advisor.use_statement_tools. The totals are not changed here (the family edits them in Accounts): the lines allocate them, their sum per flow may not exceed the account's total (409 lines_exceed_total with lines and total), and what they leave is unallocated. account is the account's name and member exactly as the month's cash flow holds them (409 account_not_in_month otherwise); amounts are in the account's currency; each category once, never the reserved loan_payment one. It REPLACES the account's lines of that month; an empty items list clears them. Confirm the numbers with the user before saving.

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": {
      "month": "<month>",
      "account": "<account>",
      "items": "<items>"
    },
    "name": "save_account_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
monthYesThe closed month, YYYY-MM
accountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With only readOnlyHint=false supplied, the description carries the burden well: it discloses REPLACE semantics, that an empty items list clears lines, that totals are not mutated, that leftovers become unallocated, and names three distinct 409 failure modes. It stops short of describing the success response shape or ordering, but the behavioral surface is otherwise unusually well covered.

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?

Front-loaded with the verb, resource, and month constraint, then error modes and parameter rules in descending importance. It is dense and some sentences pack multiple clauses, but every clause carries operational meaning and nothing reads as filler.

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?

For a three-parameter mutation tool with nested objects, no output schema, and minimal annotations, the definition covers preconditions, validation failures, replace-vs-append behavior, currency semantics, and the human-confirmation step. An agent has everything needed to call it correctly or avoid it in the wrong month.

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?

Schema coverage is only 33%, and the description compensates: 'account' must be the name and member exactly as the month's cash flow holds them, amounts are in the account's currency, each category may appear once, the reserved loan_payment category is forbidden, and items are constrained by the account total. These constraints go well beyond the schema's structural validation.

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?

States a specific verb and resource ('Saves an account's lines by category') plus the precise scope ('a CLOSED month before the first open month of the wizard queue'). The parenthetical clarifies what the lines represent ('what that month's account totals were made of'), separating it from statement tools and category-spending tools.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use preview_statement / commit_statement for the first open month, and this tool refuses that month and later with a named 409 code. It also names the alternative workflow for editing totals ('the family edits them in Accounts') and adds a procedural instruction to confirm numbers with the user first.

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