Monarch Money MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Transaction Details

get_transaction_details

Read-only

Fetch a transaction's split linkage, amount, merchant, and category_id by ID. Returns parent_transaction_id or split_transaction_ids and flags for use before split operations.

Instructions

Get one transaction's split linkage, amount, merchant, and category_id.

Compact get_transactions/search_transactions results omit split flags. Verbose results identify split legs with isSplitTransaction but do not expose their parent IDs. This tool returns a leg's parent_transaction_id or a parent's has_split_transactions flag and split_transaction_ids. Use these IDs to fetch details for individual legs; an unsplit transaction or a split leg returns an empty list.

Use this before get_transaction_splits or update_transaction_splits when you need the parent ID. transaction_id is the resolved ID returned by Monarch; it may differ from the requested ID when a pending transaction redirects to its posted replacement. Missing transactions raise an error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`transaction_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`amount`	Yes
`merchant`	Yes
`category_id`	Yes
`transaction_id`	Yes
`is_split_transaction`	Yes
`parent_transaction_id`	Yes
`split_transaction_ids`	Yes
`has_split_transactions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.2Sep 30, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare this is a read-only, non-open-world operation, and the description adds important behavioral context beyond that: missing transactions raise an error, pending transactions may redirect to a posted replacement, and the returned IDs may differ from the requested transaction_id.

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?

The description is front-loaded with the core purpose, then provides necessary split-related context, usage guidance, and parameter semantics. Although it is fairly detailed, every sentence adds distinct operational information for invoking and interpreting the tool.

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?

Given that an output schema exists, the description need not explain the full return shape. It still supplies critical context about return values, empty-list behavior, ID resolution, and error behavior, making the definition complete for correct invocation.

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 only one parameter and 0% schema description coverage, the description carries the full burden. It describes transaction_id as the resolved ID returned by Monarch and explains that it may differ from the requested ID when a pending transaction redirects to its posted replacement.

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 first sentence states a specific verb and resource: getting one transaction's split linkage, amount, merchant, and category_id. It also explicitly differentiates this tool from get_transactions and search_transactions by explaining what those compact and verbose results omit.

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?

The description gives clear when-to-use guidance: use this before get_transaction_splits or update_transaction_splits when you need the parent ID. It also explains when the return is empty, so the agent knows what outcome to expect for unsplit transactions and split legs.

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