goodwill-mcp

Find spending not yet in Splitwise

find_missing_expenses

Read-onlyIdempotent

Compare card or bank transactions against Splitwise and identify which expenses are missing from your records, so you can add them.

Instructions

Check a list of card or bank transactions against Splitwise and report which ones have not been added yet. Paste a statement and read the rows into the transactions argument; this tool does the matching. A transaction counts as already logged when an expense you paid for matches it on amount, currency and date. Read-only: it never adds anything, it only tells you what is missing so you can add it with add_expense.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`currency`	No	Currency of the statement, unless a row overrides it.	USD
`group_id`	No	Limit the comparison to one group. Otherwise checks all your expenses.
`window_days`	No	How far either side of the statement dates to look for a match.
`transactions`	Yes	Rows from a statement. Only charges you paid; ignore refunds and incoming payments.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`checked`	Yes
`missing`	Yes
`already_logged`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context by explaining the exact matching criteria (amount, currency, date) and reinforcing that the tool never adds anything, which is consistent with 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?

Three focused sentences cover purpose, input method, matching logic, and read-only behavior. The most important information is front-loaded, and every sentence contributes value without redundancy.

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?

The tool is fully specified for an agent to use correctly: purpose, input workflow, matching rules, read-only behavior, and the follow-up action are all present. With complete schema coverage and an output schema, no critical context is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics: it explains that the transactions argument should contain statement rows and defines how a match is determined. This goes beyond the schema's field descriptions.

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 states a specific verb and resource: check card/bank transactions against Splitwise and report which have not been added. It clearly distinguishes itself from add_expense by emphasizing detection rather than creation, and the title reinforces the purpose.

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?

It explicitly describes when to use the tool (when you have a statement to compare against Splitwise) and when not to use it for adding expenses, directing the agent to add_expense for the missing items. This gives practical workflow guidance and names the relevant alternative.

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

Deploy Server