Tally

Settle up

settle_up

Record a payment from one person to another to settle a shared expense.

Instructions

Record that one person paid another back.

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": {
      "amount": "<amount>",
      "to": "<to>"
    },
    "name": "settle_up"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Who received the money
`amount`	Yes	How much changed hands
`paid_by`	No	Who paid. Omit when the speaker paid.
`idempotency_key`	No	Repeat unchanged when resending; omit otherwise.

Output Schema

Name	Required	Description	Default
`settle`	Yes
`summary`	Yes
`balances`	Yes
`household`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

B3/5.0

Behavior2/5

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

The description only says 'record', which implies a write operation, but provides no details on side effects, idempotency, or whether balances are updated. Since annotations provide no hints (all false), the description carries the full burden but falls short.

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 a single, concise sentence that contains no unnecessary words. It is well-structured and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal and does not explain what 'settle up' entails in a larger expense-tracking context, such as whether it updates balances or creates a transaction. This ambiguity could confuse an agent, especially with several sibling tools that overlap in 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?

The tool description adds no additional meaning to the parameters; the schema already fully describes each parameter. With 100% schema coverage, the baseline is 3, and the description does not enhance it.

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 clearly states the tool's purpose: recording that one person paid another back. It is specific and distinct from sibling tools like record_expense, which handles shared expenses, making the tool's function unambiguous.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives such as record_expense or what_do_i_owe. The description offers no context for choosing this tool over others.

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

Deploy Server