Skip to main content
Glama
trustxai

amazing-splitwise-mcp

by trustxai

splitwise_get_expenses

Read-onlyIdempotent

List Splitwise expenses newest first, filtered by group, friend, or date range, to review spending and find expense IDs for updates.

Instructions

List expenses, newest first, optionally filtered by group, friend and date range.

Calls GET /get_expenses. Splitwise includes DELETED expenses in this list; they are hidden by default and the response says how many were hidden (include_deleted=true shows them, tagged [deleted]). Settle-up payments are tagged [settle-up]. Each row shows the date, description, full cost, group, who paid (shares with paid_share > 0) and — when current_user_id is given — your net on that expense.

Sign convention: "Your net" is your net_balance on the expense; positive = owed to you (you paid more than your share), negative = you owe.

When to Use:

  • "What did we spend in the Lima trip group?" (group_id) or "expenses with Ana" (friend_id).

  • Finding an expense id before reading, updating or deleting it.

  • Reviewing recent activity in a date window (dated_after / dated_before).

When NOT to Use:

  • To see one expense's full split, repayments and comments (use splitwise_get_expense).

  • To get balances per friend or per group (use splitwise_get_balances / splitwise_get_group_balances).

  • To turn a group or friend NAME into an id (use splitwise_resolve_group / splitwise_resolve_friend).

Returns: Markdown: a table | id | Date | Description | Cost | Group | Paid by | (Your net) | plus the hidden-deleted count and the next offset. JSON: {count, returned_by_api, hidden_deleted, limit, offset, has_more, next_offset, expenses: [raw expense objects]}.

Pagination: limit (1-100, default 20) is sent to Splitwise; has_more is true when Splitwise returned a full page, and the next offset is offset + rows returned by Splitwise (deleted rows count toward it even when hidden). Markdown shows at most 50 rows; the note under the table gives the offset to continue from.

Examples:

  • params = {"group_id": 12345, "dated_after": "2026-09-01"}

  • params = {"friend_id": 678, "limit": 50, "current_user_id": 491923}

  • params = {"limit": 20, "offset": 20, "response_format": "json"}

Error Handling: Passing both group_id and friend_id is refused (Splitwise would ignore friend_id). 401 → API key missing/regenerated; 403 → you are not a member of that group; 429 → back off for Retry-After seconds.

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, and the description adds genuinely non-obvious behavior: deleted expenses are returned but hidden and counted, tagged '[deleted]' / '[settle-up]', the net-balance sign convention, refusal when group_id and friend_id are both passed, and 401/403/429 handling with Retry-After.

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?

Front-loaded core purpose and well-organized with headings, but the Returns section substantially duplicates the output schema and the Pagination paragraph restates the schema's limit default, making it longer than strictly necessary.

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?

Covers filtering, pagination, response formats, mutual exclusion, tags and error codes; since an output schema exists, the return-format detail is a bonus rather than a gap. An agent has everything needed to call this correctly.

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?

Adds meaning well beyond the schema: the sign convention for current_user_id's 'Your net' column, that deleted rows still consume the offset, that markdown caps at 50 rows, and that group_id/friend_id are mutually exclusive and refused. This is interpretive information the schema alone cannot convey.

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?

Opens with a specific verb, resource, ordering and filter scope: 'List expenses, newest first, optionally filtered by group, friend and date range.' Combined with the When NOT to Use section that names splitwise_get_expense, splitwise_get_balances and splitwise_get_group_balances, an agent can distinguish this from every sibling without opening a schema.

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?

Gives explicit positive cases (cost per group, expenses with a friend, finding an id before update/delete, date-window review) and negative cases with named alternatives for each. Nothing about when to choose this tool is left to inference.

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