Skip to main content
Glama
trustxai

amazing-splitwise-mcp

by trustxai

splitwise_delete_comment

DestructiveIdempotent

Delete a comment from a Splitwise expense by its comment ID; removal is permanent, so verify the ID before deleting.

Instructions

Delete a comment from a Splitwise expense (destructive; comments have no undelete).

Write — refused unless SPLITWISE_ALLOW_WRITES=1. Calls POST /delete_comment/{id}. Splitwise answers with the deleted comment, which this tool renders so you can see exactly what was removed. There is NO undelete for comments in the Splitwise API — if needed, re-post the text with splitwise_create_comment (it gets a new id and a new timestamp).

When to Use:

  • To remove a comment you posted by mistake (get its id from splitwise_get_comments).

When NOT to Use:

  • To delete the expense itself — use splitwise_delete_expense.

  • When you only know the comment's text — list them with splitwise_get_comments first.

Returns: A confirmation echoing the deleted comment as Splitwise returned it: id, expense id, author, type, created/deleted times and the text.

Examples:

  • params = {"comment_id": 79800950}

Error Handling: Refused with Error: … writes are disabled unless SPLITWISE_ALLOW_WRITES=1. 404 = the comment id does not exist or is already gone; 403 = you are not allowed to delete it (you are not part of that expense). Errors come back as an Error ... string, never raised.

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?

Goes well beyond the annotations by disclosing the write gate (SPLITWISE_ALLOW_WRITES=1), the underlying endpoint, the absence of any undelete in the Splitwise API, and the recovery path (re-post with splitwise_create_comment, new id/timestamp). It also maps 404 and 403 to concrete causes, which the destructiveHint/idempotentHint 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 operation and its destructive nature, then cleanly sectioned into usage, returns, examples, and errors. It is longer than strictly necessary, and the 'Returns' block largely restates what the output schema already declares, but no section is 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 everything an agent needs to invoke this correctly: the required id and where to get it, the environment gate that will refuse the call, what the confirmation contains, and how each error class should be interpreted. The presence of an output schema makes the Returns section a bonus rather than a gap.

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?

Only one parameter, and the schema already describes comment_id and its source. The description reinforces the id's provenance ('get its id from splitwise_get_comments') and supplies a literal example payload, adding modest but real value over the schema alone.

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 ('Delete a comment from a Splitwise expense') and immediately scopes it against siblings by naming splitwise_delete_expense and splitwise_create_comment as different operations. An agent can distinguish this from every other delete tool in the family 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 explicit 'When to Use' and 'When NOT to Use' sections, names the sibling to use instead for each excluded case (splitwise_delete_expense for the expense itself, splitwise_get_comments when only the text is known), and routes the agent to the prerequisite call that supplies the required id.

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