splitsmart-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_groupA | Create a group with a name and a list of unique member names. |
| list_groupsA | List all groups (id and name). |
| get_groupB | Get a group with its members and expenses. |
| add_memberC | Add a new member to an existing group. |
| add_expenseA | Record an expense paid by |
| delete_expenseC | Delete an expense from a group. |
| get_balancesB | Net balance per member in cents: positive = is owed money, negative = owes money. |
| settle_upA | Minimal list of transfers (from, to, amount_cents) that settles every debt in the group. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct operation: group lifecycle (create/list/get), member addition, expense add/delete, and balance/settlement. No overlap or ambiguity between tools.
All tools follow a consistent lowercase snake_case verb_noun pattern (e.g., add_expense, get_balances). Even settle_up, a phrasal verb, fits the style without deviation.
With 8 tools, the server is well-scoped for an expense-splitting domain. Each tool is necessary for core workflows, and the count is neither sparse nor bloated.
The tool surface covers the full cycle: create/list/get groups, add members, add/delete expenses, and compute balances/settlements. Minor gaps exist (e.g., no update/delete for groups or member removal), but they are not essential for the core purpose and agents can work around them.