Skip to main content
Glama
trustxai

amazing-splitwise-mcp

by trustxai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

splitwise_health_check

Read-onlyIdempotent

Verify Splitwise API key connectivity, check write permissions, and identify your user account to debug 401 errors or prepare expense shares.

Instructions

Verify connectivity and the API key against Splitwise, and report the write kill-switch.

Calls GET /get_current_user with the configured personal API key and renders who you are logged in as (name, id, email, default currency, locale, unread notifications). Also states whether writes are enabled (SPLITWISE_ALLOW_WRITES).

When to Use:

  • As the first call after configuring the server, to confirm the key works.

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

  • To debug a 401 (key missing / regenerated) before trying other tools.

When NOT to Use:

  • To read balances (use splitwise_get_balances / splitwise_get_friends).

  • To change profile settings (use splitwise_update_user).

Returns: A markdown block with the base URL, the kill-switch state, connectivity, and the current user — or an Error ... string describing the failure.

Error Handling: 401 means the key is missing, mistyped, or was regenerated at https://secure.splitwise.com/apps; a connection error means the API URL or the network is wrong. Without a configured key the tool returns the config state and says what to set, without calling the API.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial context beyond them: the SPLITWISE_ALLOW_WRITES kill-switch, the exact endpoint called, the 401 remediation path, and the fallback behavior when no key is configured (returns config state without hitting the API).

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 and cleanly sectioned with headers, which suits an agent scanning for a diagnostic tool. It is slightly long — the Returns section partially overlaps the existing output schema — but every block still carries operational value.

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?

For a zero-param diagnostic tool with an output schema, this is fully complete: it discloses the endpoint, the kill-switch, error semantics (401 vs connection error), and no-key behavior. An agent has everything needed to call it and interpret both success and failure.

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 tool takes zero parameters, so per the rubric the baseline is 4. Nothing about argument semantics needs explaining, and the description correctly stays silent on params rather than inventing meaning.

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 ('Verify connectivity and the API key against Splitwise, and report the write kill-switch') and even names the endpoint it calls (GET /get_current_user). It explicitly distinguishes itself from siblings like splitwise_get_balances and splitwise_get_current_user by defining its diagnostic role.

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' (first call after config, learn own user id, debug 401) and 'When NOT to Use' sections with named alternatives for each exclusion. Nothing is left to inference about when this tool is the right pick.

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

Deploy Server

Other Tools