Skip to main content
Glama
AzeemWaqarRao

Splitwise MCP Server

create_expense

Create a new expense in Splitwise with equal or custom splits. Specify cost and description, optionally add group, users, date, currency, category, and details.

Instructions

Create a new expense.

cost is a decimal string, e.g. "25.00". description is required.

Splitting:

  • Equal split (default): leave users empty; the cost is split evenly among everyone in the resolved group (group_id or SPLITWISE_GROUP_ID).

  • Custom split: pass users, a list of dicts each like {"user_id": 123, "paid_share": "25.00", "owed_share": "12.50"}. Identify a user by user_id, or by email/first_name/last_name. The paid_share values must sum to cost, and so must the owed_share values.

date accepts ISO 8601 (e.g. "2026-06-15T00:00:00Z"). currency_code is a 3-letter code (e.g. "USD"). category_id and details are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
costYes
dateNo
usersNo
detailsNo
group_idNo
category_idNo
descriptionYes
currency_codeNo
split_equallyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so the description must cover behavior. It details splitting logic and date format but does not mention success responses, error conditions, permissions, or side effects.

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 well-structured with clear sections for splitting, date, currency. Every sentence adds value without redundancy.

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 9 parameters and 2 required, the description covers all parameters effectively. Output schema exists, so return values need not be detailed here.

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?

Schema coverage is 0%, so the description provides essential semantics: cost as decimal string, users as list of dicts with specific keys, date as ISO 8601, and default behavior when users is empty.

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 starts with 'Create a new expense.' and explains the resource and action clearly. It distinguishes from siblings (delete, get, list, update) by focusing on creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It explains when to use equal split versus custom split and mentions the group_id needed. It could explicitly state that this is for new expenses only, but context from sibling tools helps.

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/AzeemWaqarRao/splitwise-mcp'

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