Smart Expense Management MCP

by neev-25

Overview Schema Source Related Servers Discussions Admin

Python

Local

event_summary

Summarize an event with all expenses, member net balances, and minimal settlement transactions to resolve debts.

Instructions

Complete event summary including:

All expenses
Per-member net balances
Minimum settlement transactions (who pays whom, how much)

This uses the greedy two-pointer algorithm to minimize the number of transactions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "event_summary"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Discloses that the algorithm is 'greedy two-pointer' to minimize transactions. Although no annotations exist, this addition provides useful behavioral context beyond a generic summary.

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?

Efficient bulleted list plus a brief algorithm note. Every sentence adds value with no 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?

Given the presence of an output schema, the description adequately covers the tool's output components (expenses, balances, settlements) and algorithmic detail, making it complete for its purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has one parameter (event_id) with 0% description coverage. The description does not explicitly describe event_id, but its purpose is inferable from context. Baseline for low coverage is 3, as description adds limited 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?

Clearly states it provides a complete event summary including expenses, net balances, and settlement transactions. Distinct from sibling summary tools by specifying comprehensive components.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage as the go-to for overall event financial summary, but no explicit guidance on when to use alternative tools like expense_summary or settle.

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