Skip to main content
Glama
erikrubstein

monarch-mcp2

by erikrubstein

Receipts Update Receipt

receipts_update_receipt

Update an existing receipt in Monarch Money by providing its ID and optionally modifying merchant, date, totals, or line items.

Instructions

Update receipt. This may create or update Monarch data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taxNo
tipNo
dateNo
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
line_itemsNo
receipt_idYes
grand_totalNo
output_modeNoOutput shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.summary
session_pathNo
merchant_nameNo
total_before_taxNo
transaction_dateNo
transaction_totalNo
Behavior3/5

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

Annotations indicate a non-destructive, non-idempotent mutation. The description adds 'may create or update Monarch data,' hinting at side effects but lacks detail on conditions or outcomes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two clauses) but lacks structure. It is concise but at the expense of necessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 parameters, no output schema, and low schema coverage, the one-sentence description is wildly incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 15% schema coverage, the description provides no parameter explanations. It does not compensate for the many undocumented optional fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update receipt' clearly states the action and resource. It distinguishes from receipt siblings like delete, get, and list.

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 versus alternatives like upload, match, or unmatch. The description does not specify prerequisites or exclusions.

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/erikrubstein/monarch-mcp2'

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