splitwise_resolve_group
Converts a group name into its Splitwise group id with ranked fuzzy candidates and an exact, probable, or ambiguous verdict, so you confirm the right group before creating expenses.
Instructions
Turn a group's name into its Splitwise group id, with ranked fuzzy candidates.
Calls GET /get_groups (not cached — groups change) and scores every group name with
difflib.SequenceMatcher on case- and accent-folded text. Returns the top limit
candidates with their scores. Group id 0 is Splitwise's pseudo-group for non-group
expenses (group_id: 0 = no group).
A group is resolved ONLY on an exact name match (1.000, for exactly one group, and no other group name starting with the query — "Peru trip" next to "Peru trip 2026" is ambiguous). A close-but-not-exact name is reported as probable and must be confirmed with the user; a query whose numbers differ ("peru trip 2025" vs "Peru trip 2026") or that is under 4 characters gets no fuzzy candidate at all.
When to Use:
Before
splitwise_create_expense,splitwise_get_group,splitwise_get_expenses,splitwise_add_user_to_grouporsplitwise_delete_group, when the user named a group ("the Peru trip").
When NOT to Use:
To list every group with balances — use
splitwise_get_groups.For people or categories — use
splitwise_resolve_friend/splitwise_resolve_category.
Returns:
The resolution line plus a markdown table (rank, Name (id N), type, members, score);
or, with response_format json, {query, resolution, ambiguous_count, reason, resolved, probable, candidates: [{id, name, group_type, members_count, pseudo_group, score}]} where resolution is exact | probable | ambiguous | none,
ambiguous_count (always present, 0 unless ambiguous) says how many candidates are in
contention, resolved is set only for exact, and probable only for probable.
Examples: params = {"query": "peru trip"} params = {"query": "home", "limit": 3, "response_format": "json"}
Error Handling:
A 401 means the API key is missing or was regenerated. With no groups the tool says
so. Anything but exact means: ask the user, do not pick.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |