Skip to main content
Glama
svarun115

Splitwise MCP Server

by svarun115

splitwise_create_expense

Create an expense and split costs equally or assign custom shares to group members with paid and owed amounts.

Instructions

Create a new expense. Can split equally among group members or specify custom shares for each user. For custom shares, provide users array with paid_share and owed_share for each user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
costYesTotal cost as a decimal string (e.g., "25.00")
dateNoDate of expense (ISO 8601 format). Defaults to now.
usersNoArray of user share objects (required if not splitting equally). Each must have paid_share, owed_share, and either user_id or email/first_name/last_name
detailsNoAdditional notes about the expense
group_idNoGroup ID (0 for expenses outside a group)
category_idNoCategory ID from get_categories
descriptionYesShort description of the expense
currency_codeNoCurrency code (e.g., "USD")
split_equallyNoWhether to split equally among group members
repeat_intervalNoRepeat frequency
Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses that the tool creates an expense and splits options, but fails to mention side effects, authorization needs, or return behavior. More detail on what happens upon creation is needed.

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 two concise sentences. The first sentence states the core purpose, and the second expands on the key parameter behavior. No wasted words.

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

Completeness3/5

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

Given 10 parameters (2 required) and no output schema, the description adequately covers the splitting logic but omits explanation of many optional parameters (e.g., repeat_interval, category_id) and the return value. It is minimally complete.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds value by clarifying the purpose of the users array for custom shares and implying that split_equally negates the need for users. This goes beyond the schema descriptions.

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 'Create a new expense' with a specific verb and resource. It also distinguishes between equal splits and custom shares, differentiating this create tool from related siblings like update, delete, and get.

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?

The description explains when to use equal splitting vs. custom shares, providing clear context. However, it does not explicitly mention prerequisites (e.g., needing a group ID) or alternative tools for other operations.

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

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