Housewarden

Add bill

add_bill

Record a bill with name, amount, due date, and optional monthly or yearly recurrence to manage household expenses.

Instructions

Adds a bill with an amount and due date, optionally recurring. Needs the name, amount and due date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	What the bill is for, e.g. Electricity.
`amount`	Yes	Amount in major units, e.g. 3000 or 45.5.
`member`	No	Who is asking, if known: a member id or name. Used for per-member policies and the audit trail.
`dry_run`	No	When true, return the preview only. Nothing is written and nothing is queued.
`currency`	No	ISO-4217 code; defaults to the household currency.
`due_date`	Yes	YYYY-MM-DD in the household timezone.
`recurrence`	No	none, monthly or yearly.	none
`idempotency_key`	No	Optional client-chosen key. Repeating a call with the same key returns the original outcome instead of acting twice.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already signal that this is a write operation (readOnlyHint=false), and the description aligns by saying 'Adds'. It adds the useful behavioral note that bills can be recurring, but it does not disclose the dry_run no-write path, idempotency behavior, or audit-trail implications. The schema covers some of these, so the description is minimally adequate but not rich.

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?

The description is short and front-loaded, with no filler. The second sentence is somewhat redundant with the schema's required fields, but it is still clear and quick to parse.

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

Completeness3/5

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

The tool has eight parameters and an output schema, and the schema itself documents all parameters well. However, the description does not explain important behavioral options like dry_run or idempotency_key, leaving the agent to rely entirely on parameter descriptions for those nuances.

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 description coverage is 100%, so the baseline is 3. The description adds little beyond the schema, merely echoing that name, amount, and due date are needed and that recurrence is optional. No new parameter semantics are provided.

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 uses a specific verb ('Adds') with a clear resource ('a bill') and identifies the core fields (amount, due date, optional recurrence). This makes it easy to distinguish from siblings like update_bill, mark_bill_paid, and list_bills.

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

Usage Guidelines2/5

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

The description states the required inputs ('name, amount and due date') but gives no guidance on when to use this tool versus update_bill, mark_bill_paid, or other bill-related tools. It does not mention any exclusion conditions or alternatives.

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