Skip to main content
Glama
jamiew

Monarch Money MCP Server

Create Transaction

create_transaction

Add a new manual transaction to your financial records. Input amount, merchant, account, date, category, and optional notes; choose whether to update account balance.

Instructions

Create a new manual transaction.

Args: amount: Transaction amount (positive for income, negative for expense) merchant_name: Name of the merchant/payee (e.g., "Starbucks", "Monthly Rent") account_id: ID of the account for this transaction date: Transaction date in YYYY-MM-DD format category_id: ID of the category to assign (required for new transactions) notes: Optional notes/memo for this transaction update_balance: Whether to update account balance when creating this transaction (default: False) - False: Transaction is recorded but doesn't affect account balance (typical for synced accounts) - True: Adjusts account balance by transaction amount (useful for manual accounts)

Returns: JSON string with created transaction details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
merchant_nameYes
account_idYes
dateYes
category_idYes
notesNo
update_balanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
transactionYes
Behavior4/5

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

Annotations declare readOnlyHint=false, so the agent knows this is a write operation. The description adds value by explaining the update_balance parameter's effects, confirming it mutates account balance when true. It also mentions the return format (JSON string). However, it does not explicitly state that the operation is not idempotent, which matches the idempotentHint=false annotation.

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 well-structured with a clear opening line and bullet-style parameter explanations. Every sentence adds value, though the update_balance explanation could be slightly condensed without losing meaning.

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 has 7 parameters and an output schema (declared), the description covers the creation action, all parameter meanings, return type, and a key behavioral option (update_balance). Missing aspects include validation or error scenarios (e.g., invalid account_id), but the description is still fairly complete.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's meaning, format, and constraints. For example, amount is described as 'positive for income, negative for expense', date as 'YYYY-MM-DD', and update_balance with use cases.

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 explicitly states 'Create a new manual transaction,' which is a specific verb-resource combination. This clearly distinguishes it from sibling tools like update_transaction or get_transactions.

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 provides contextual guidance on when to set update_balance to True vs False based on account type (synced vs manual). However, it does not explicitly tell the agent when to use this tool over other transaction-related tools, such as syncing or importing.

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/jamiew/monarch-mcp'

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