Skip to main content
Glama
Sign In
monarch-mcp-server

monarch-mcp-server

by robcerda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_transaction

Modify an existing transaction's details such as amount, description, category, or date in Monarch Money.

Instructions

Update an existing transaction in Monarch Money.

Args:
    transaction_id: The ID of the transaction to update
    amount: New transaction amount
    description: New transaction description
    category_id: New category ID
    date: New transaction date in YYYY-MM-DD format

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "update_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
amountNo
category_idNo
descriptionNo
transaction_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations; description does not disclose side effects (e.g., what if transaction_id is invalid), authentication needs, or reversibility. Minimal behavioral context beyond the action itself.

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?

Two clear sentences plus a well-structured Args list. No filler, information is front-loaded and easy to parse.

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?

Covers basic action and parameters, but lacks return value description or error handling. With no output schema, the agent is left guessing about response format. Adequate but incomplete.

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?

Description adds meaning beyond the schema by specifying 'New transaction amount', etc., and providing date format (YYYY-MM-DD). Despite schema coverage metric of 0%, the Args list enriches parameter understanding.

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?

Clearly states 'Update an existing transaction in Monarch Money' – specific verb, resource, and platform. Distinct from sibling tools like create_transaction and 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 Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., create_transaction). No mention of prerequisites or conditions for updating.

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

Deploy Server

Other Tools