Skip to main content
Glama
chrischall

splitwise-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sw_update_user

Destructive

Update your Splitwise profile name, locale, and default currency after user approval. Account credentials remain unchanged.

Instructions

Update the current user's profile fields: name, locale and default currency. id must be the current user's id. The login email and password are deliberately not settable here — account credentials are changed in the Splitwise app, not by an assistant. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUser ID (must be the current user's id)
localeNo
last_nameNo
first_nameNo
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
default_currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.2.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv3.1.2
    • removedInput schema / properties / email
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / password
      Removed value: -{
-  "type": "string"
-}
  3. Changed1 schema field changedv3.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observedv2.1.5

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish that this is a mutating operation (readOnlyHint=false, destructiveHint=true), so the description does not need to restate that. It adds meaningful behavioral context: the confirmation requirement, the confirmToken handshake, and the credential exclusion. It could further clarify whether omitted fields are left unchanged, but it still provides substantial transparency beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two dense sentences with no filler. The core operation comes first, followed by the identity constraint, the credential exclusion, and the confirmation protocol. Referencing MCP_CONFIRM_MODE avoids repeating platform mechanics. Every clause earns its place.

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 six-parameter mutating tool with no output schema, the description covers the required fields, the current-user restriction, the intentionally non-settable fields, and both confirmation paths. An agent has enough information to decide whether to call it, what arguments to pass, and how to complete the two-step confirmation fallback. The key return behavior is described precisely as needed.

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?

With only 33% schema description coverage, the description carries real weight for parameter meaning. It names the domain fields (name, locale, default currency) and explains the confirmToken lifecycle, which is the tool's most subtle parameter. It slightly underspecifies by collapsing first_name and last_name into 'name,' and it doesn't give locale/currency formats, but it compensates well overall for a low-coverage schema.

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?

The description opens with a specific verb and resource — 'Update the current user's profile fields' — and enumerates the exact updatable areas: name, locale, and default currency. The restriction 'id must be the current user's id' removes ambiguity about scope and distinguishes this from any other user-oriented operation. An agent can tell immediately what this tool does and what it does not do.

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?

The description explicitly sets a boundary: login email and password are 'deliberately not settable here' and belong to the Splitwise app, not an assistant. It also explains the confirmation workflow, including the fallback path where the first call returns a preview and confirmToken and only a repeat call proceeds. This gives an agent clear when-to-use and when-not-to-use guidance.

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