Skip to main content
Glama
trustxai

amazing-splitwise-mcp

by trustxai

splitwise_get_current_user

Read-onlyIdempotent

Retrieve your own Splitwise user id, email, default currency, locale, and unread notification count to build expense shares or update your profile.

Instructions

Get the Splitwise user the API key belongs to: name, id, email, currency, locale, notifications.

Calls GET /get_current_user and renders your name and id (as First Last (id N), so the id can be chained into other tools), email, registration status, default currency, locale, the unread notifications count, when notifications were last read, and your email-notification settings (expense_added=on, …).

When to Use:

  • To learn your own user id before building expense shares or updating your profile.

  • To check your default currency or locale before creating expenses.

  • To see how many unread notifications you have (read them with splitwise_get_notifications).

When NOT to Use:

  • To check the API key / kill-switch state (use splitwise_health_check).

  • To look up someone else (use splitwise_get_user, or splitwise_resolve_friend for a name → id).

  • To read balances (use splitwise_get_balances / splitwise_get_friends).

  • To change your name, locale or default currency (use splitwise_update_user).

Returns: Markdown (default): a bullet list with the fields above. JSON: the raw Splitwise current_user object (incl. picture, notifications_read, notifications).

Examples:

  • params = {}

  • params = {"response_format": "json"}

Error Handling: 401 means SPLITWISE_API_KEY is missing, mistyped or was regenerated at https://secure.splitwise.com/apps. 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/openWorld, so only additive context is needed, and the description delivers: 401 means the API key is missing/mistyped/regenerated (with the URL to fix it), every failure returns an `Error ...` string, and the markdown rendering is shaped as `First Last (id N)` specifically so the id can be chained into other tools. This is genuinely useful behavior an agent cannot get from the annotations or schema.

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?

Well front-loaded and clearly sectioned (When to Use, When NOT to Use, Returns, Examples, Error Handling), so an agent can scan it. However, the field enumeration in the opening paragraph largely repeats the fuller enumeration in Returns, which is mild redundancy in an otherwise efficient layout.

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 an output schema exists, the description already exceeds the bar by documenting return shapes and error semantics. Combined with explicit routing to siblings, examples, and auth failure behavior, an agent has everything needed to select and call this tool correctly.

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 single `response_format` parameter is given concrete invocation examples (`params = {}` and `params = {"response_format": "json"}`), and the Returns section explains what each mode produces, which goes beyond the bare schema description. It does not add much more than the schema already states about the enum, so not a 5.

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?

States a specific verb and resource ('Get the Splitwise user the API key belongs to') and enumerates the returned fields (name, id, email, currency, locale, notifications). It also implicitly distinguishes itself from `splitwise_get_user` by scoping to the API key's owner, which the When NOT to Use section makes explicit.

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?

Provides explicit When to Use and When NOT to Use lists, each naming the concrete alternative for the excluded case (`splitwise_health_check` for key state, `splitwise_get_user` / `splitwise_resolve_friend` for other people, `splitwise_get_balances` / `splitwise_get_friends` for balances, `splitwise_update_user` for edits). Nothing is left to inference.

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