Skip to main content
Glama
Sign In

SwiftProbate

by com.swiftprobate
OverviewDiscussionsAdmin

log_transaction

Record a financial transaction in the estate ledger when the user mentions money moving — an expense they paid, income the estate received, a debt payment, or a distribution to an heir. Examples: "I paid $4,200 for the funeral", "the estate got a $1,300 tax refund", "my brother covered the $800 headstone". ALWAYS confirm the amount, what it was for, and (for expenses) who paid before calling. Administration expenses are direction='disbursement'. If someone paid out of pocket, set paid_by='individual' so it's tracked as reimbursable: leave payer_name empty if the user themselves paid, or set payer_name to the person's name if someone else (e.g. a family member who isn't the estate) paid. Records a bookkeeping entry only; does not move money. Duplicate detection is time-limited, so repeating later may add another entry.

Input Schema

NameRequiredDescriptionDefault
notesNoOptional free-text note.
amountYesPositive dollar amount (the direction conveys whether it's in or out).
heir_idNoOptional ID of the heir who received a distribution.
paid_byNoOnly for disbursements. 'individual' means a person paid out of pocket and is owed reimbursement (the user, unless payer_name is given). Defaults to 'estate'.
asset_idNoOptional ID of a related asset (e.g. sale proceeds from a specific account or property).
categoryYesFor disbursement: funeral, court_fees, attorney_fees, executor_fee, property_maintenance, appraisal, insurance, taxes, debt_payment, other_expense. For receipt: opening_balance (physical cash or funds NOT held in a bank account that's been added as an asset — for a bank account's date-of-death balance, set that asset's date_of_death_value instead (on create_asset when recording the account, or update_asset if it already exists); it flows into the ledger's starting balance automatically), asset_collected (funds brought into the estate from the decedent's holdings, e.g. closing an account or life insurance payable to the estate — but NOT internal transfers between the estate's own accounts), income_dividend, income_interest, income_rent, refund, asset_sale (record the full gross sale price; log payoffs/closing costs as separate disbursements), other_receipt. For distribution: cash_distribution, asset_distribution.
directionYes'receipt' = money into the estate; 'disbursement' = money out, including expenses and debt payments; 'distribution' = money/assets paid to an heir.
estate_idYesThe estate to act on. Call list_my_estates first to get this id.
payer_nameNoOnly when paid_by='individual' AND someone other than the user paid (e.g. a family member). The person's name. Omit if the user themselves paid.
document_idNoOptional ID of a document (e.g. a receipt or invoice the user uploaded) to attach to this transaction as its receipt. The document is treated as a ledger receipt and kept out of the Documents library.
payee_or_sourceNoWho was paid (for money out) or the source (for money in), e.g. 'Travis County Clerk' or 'Fidelity dividend'. Optional.
transaction_dateNoDate the money moved, as YYYY-MM-DD. Omit when it moved today — today is then taken in the user's time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / transaction_date / description
      Previous value: -"Date the money moved, as YYYY-MM-DD."New value: +"Date the money moved, as YYYY-MM-DD. Omit when it moved today — today is then taken in the user's time zone."
    • changedInput schema / required
      Previous value: -[
-  "estate_id",
-  "direction",
-  "category",
-  "amount",
-  "transaction_date"
-]New value: +[
+  "estate_id",
+  "direction",
+  "category",
+  "amount"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations: it explicitly says the tool records a bookkeeping entry only and does not move money, and that duplicate detection is time-limited so a repeat call may create a second entry — directly explaining the non-idempotent behavior declared in annotations rather than contradicting it.

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?

Front-loaded with the core purpose, then examples, then the confirmation prerequisite, then the edge-case notes (bookkeeping-only, duplicate behavior). Every sentence carries actionable information and none are redundant with the schema.

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?

For a 12-parameter mutation with no output schema, it covers the critical gaps: mutation semantics, duplicate risk, required confirmation, and payer attribution. It does not say what is returned on success (e.g. a transaction id), which would help an agent chain into update_transaction, so it falls just short of complete.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic guidance: administration expenses map to direction='disbursement', and paid_by='individual' vs empty payer_name vs named payer_name encodes the reimbursement logic that the schema only partially conveys.

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 ('record a financial transaction in the estate ledger') and enumerates the scenarios that qualify (expense, income, debt payment, distribution), which cleanly separates it from read-only siblings like get_transactions and from update_transaction.

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?

Gives a clear trigger ('when the user mentions money moving') plus realistic example utterances and a mandatory pre-check ('ALWAYS confirm the amount, what it was for, and who paid'). It does not explicitly name alternatives such as update_transaction for correcting an existing entry, so it stops short of a 5.

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

All SwiftProbate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources