Skip to main content
Glama
trustxai

amazing-splitwise-mcp

by trustxai

splitwise_undelete_group

Idempotent

Restore a deleted Splitwise group and its expenses by group id. Use it to reverse an accidental group deletion when writes are enabled.

Instructions

Restore a deleted group (and its expenses). 🔒 write.

Calls POST /undelete_group/{id}. Splitwise answers HTTP 200 even when this fails and puts the outcome in success / errors; the client turns a failure into an error, and this tool reports the group as restored only when the body says success: true. Refused with Error: … writes are disabled unless SPLITWISE_ALLOW_WRITES=1. Undo: splitwise_delete_group.

When to Use:

  • To bring back a group deleted by mistake (splitwise_delete_group).

When NOT to Use:

  • To restore one expense (use splitwise_undelete_expense).

  • To re-add a removed member (use splitwise_add_user_to_group).

  • With a group NAME — resolve it to an id first (use splitwise_resolve_group).

Returns: A confirmation with the success / errors values Splitwise returned — or, when the body does not say success: true, a note to verify before reporting it as restored.

Examples:

  • params = {"group_id": 12345}

Error Handling: success: false / non-empty errors come back as Error: Splitwise rejected the request ....

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the HTTP-200-with-success/errors quirk, the write gate requiring SPLITWISE_ALLOW_WRITES=1, the failure transformation into an Error, the undo path, and the refusal message text. These are exactly the behaviors an agent cannot derive from readOnlyHint/destructiveHint/idempotentHint alone.

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?

Front-loaded purpose line followed by tight labeled sections (When to Use, When NOT to Use, Returns, Examples, Error Handling). Dense but every sentence contributes actionable information with no filler.

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 mutation's failure modes, environment gating, return-value interpretation, and error surface, which is more than enough for a one-parameter write tool even though an output schema exists. An agent has everything needed to call and interpret it 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?

One required param with reported 0% schema coverage, so the description carries the burden: it supplies an example params block and, crucially, warns that a group NAME must first be resolved to an id via splitwise_resolve_group. That adds real semantic value, though it does not restate the schema's own '0 is not a real group' constraint.

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 ('Restore a deleted group (and its expenses)') and mirrors the exact endpoint POST /undelete_group/{id}. An agent can distinguish it from splitwise_delete_group and splitwise_undelete_expense without opening any 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?

Provides explicit When to Use / When NOT to Use sections and names each alternative with the condition that selects it (splitwise_undelete_expense for one expense, splitwise_add_user_to_group for re-adding members, splitwise_resolve_group for name-to-id resolution). 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.