Skip to main content
Glama
trustxai

amazing-splitwise-mcp

by trustxai

splitwise_get_user

Read-onlyIdempotent

Fetch a Splitwise user's public profile by ID to get their name, email, and registration status, turning raw ids in expenses or debts into real people.

Instructions

Get another Splitwise user's public profile by id: name, email, registration status.

Calls GET /get_user/{id}. Splitwise only answers for users you are connected to — a friend, or someone who shares a group with you — and for yourself.

When to Use:

  • To turn a user id seen in an expense, debt or notification into a name and email.

  • To check whether someone is a confirmed user or a dummy/invited placeholder.

When NOT to Use:

  • For yourself with notification settings, currency and locale (use splitwise_get_current_user).

  • To find a user id from a name (use splitwise_resolve_friend).

  • For balances with that person (use splitwise_get_friend / splitwise_get_balances).

Returns: Markdown (default): First Last (id N) <email> and the registration status (confirmed | dummy | invited). JSON: the raw Splitwise user object (incl. picture).

Examples:

  • params = {"user_id": 491923}

  • params = {"user_id": 491923, "response_format": "json"}

Error Handling: 403 when the user is neither your friend nor in a group with you; 404 when the id does not exist; 401 when the API key is missing or revoked. Every failure comes back as an Error ... string.

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description still adds a non-obvious access constraint (only friends, group co-members, or self), the underlying endpoint, the full error contract (403/404/401) and the fact that failures return as `Error ...` strings. It also distinguishes `confirmed` vs. `dummy`/`invited` user states, which the annotations cannot convey.

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 with the core purpose, then cleanly sectioned by usage, returns, examples and errors; the examples section is somewhat redundant given the schema. Well-sized overall but slightly longer than strictly necessary for a one-parameter read.

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 the access model, both output formats, the endpoint, and every failure mode. Even though an output schema exists (so return values are technically redundant here), the extra detail about the registration-status field meaning makes a one-parameter read tool fully self-contained.

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?

The schema documents both properties inline, and the description reinforces them with concrete example payloads (`{"user_id": 491923}`) plus the access precondition on user_id and the meaning of response_format. It adds example values and the friend/group requirement, though it doesn't explain edge cases beyond the schema's own notes.

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?

Starts with a specific verb+resource+scope: "Get another Splitwise user's public profile by id" and enumerates the returned fields (name, email, registration status). It explicitly names the sibling tools it is not (splitwise_get_current_user, splitwise_resolve_friend, splitwise_get_friend), so an agent can route 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?

Has dedicated "When to Use" and "When NOT to Use" sections, the latter naming four concrete alternatives with the condition that selects each (self vs. other, name-to-id vs. id-to-name, balances vs. profile). This is as explicit as routing guidance gets.

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