Skip to main content
Glama
sharph

Lunch Money MCP Server

by sharph

get_transactions

Retrieve transactions within a date range, with filters and pagination. Optionally get category aggregates for the full period.

Instructions

Get transactions for a date range.

This is a paginated tool and you MUST consider that not all transactions may be returned. The has_more return value will tell you if pagniation should continue. If has_more is true, ask yourself if you need to make another request to properly answer the user's query.

include_aggregates returns aggregates for all pages.

Args: start_date: Start date in YYYY-MM-DD format (required) end_date: End date in YYYY-MM-DD format (defaults to last day of start_date's month) filter_category_name: Filter by category name (e.g., "Groceries", "Dining Out") filter_tag_id: Filter by tag ID filter_status: Filter by transaction status (reviewed, unreviewed, delete_pending) filter_is_pending: Filter by pending status filter_manual_account_id: Filter by manual account ID filter_plaid_account_id: Filter by plaid account ID filter_recurring_id: Filter by recurring item ID include_pending: Include pending transactions (ignored if is_pending is set) limit: Maximum number of transactions to return (1-100, default 100) offset: Pagination offset include_aggregates: If True, calculates totals per category for full date range (respects all filters, except pagination)

Returns: Structured JSON where transactions include category names instead of IDs, has_more pagination flag, and optionally category aggregates. When has_more is true, next_offset and next_limit are provided for easy pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
end_dateNo
start_dateYes
filter_statusNo
filter_tag_idNo
include_pendingNo
filter_is_pendingNo
include_aggregatesNo
filter_recurring_idNo
filter_category_nameNo
filter_plaid_account_idNo
filter_manual_account_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description thoroughly discloses pagination, return structure (transactions with category names), and aggregate behavior. It provides all necessary behavioral traits.

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?

Well-structured with a clear purpose, pagination warning, parameter list, and return details. Slightly verbose but every sentence is informative. Front-loaded with essential info.

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?

Fully covers the tool's complexity: 13 params, pagination, aggregates, return format. With no annotations and an output schema present, the description is sufficient 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?

Despite 0% schema coverage, the description explains all 13 parameters with formats, defaults, and dependencies (e.g., 'include_pending ignored if is_pending set'). Adds significant value beyond the schema.

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 clearly states 'Get transactions for a date range' and details the functionality, distinguishing it from sibling tool 'get_transaction'.

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?

Explicitly instructs about pagination, how to handle 'has_more', and when to make additional requests. Also clarifies 'include_aggregates' behavior.

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/sharph/lunchmoney-mcp-mini'

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