Skip to main content
Glama

Complete a chore

chore_complete

Mark a chore round done and let the app reschedule it, rotate to the next member, and close swap requests. Pass current due date and assignee to block stale or double completions.

Instructions

Mark the current round of a chore as done by the calling member. The app schedules the next due date from the cadence, moves the chore to the next available member in the rotation (skipping absent members), and closes an open swap request for it. Call chores_list first and pass the chore's current nextDueAt and assignedMemberId as the expected values so a stale or double completion is rejected. Returns chore_occurrence_changed if the chore moved on since you read it: read again and decide again, do not retry blindly. Returns chore_already_completed if this round was just completed. Not for editing a chore: use chore_update. The response holds the updated chore and completion { id, previous { nextDueAt, assignedMemberId, anchorAt } }; keep them to take a mistaken completion back with chore_complete_undo.

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": {
      "id": "<id>",
      "expectedNextDueAt": "<expectedNextDueAt>",
      "expectedAssignedMemberId": "<expectedAssignedMemberId>"
    },
    "name": "chore_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the chore, from chores_list.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
expectedNextDueAtYesThe chore's nextDueAt exactly as returned by chores_list. Identifies the round being completed.
expectedAssignedMemberIdYesThe chore's assignedMemberId exactly as returned by chores_list, or null if it has no assignee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / expectedAssignedMemberId / description
      Added value: +"The chore's assignedMemberId exactly as returned by chores_list, or null if it has no assignee."
    • addedInput schema / properties / expectedNextDueAt / description
      Added value: +"The chore's nextDueAt exactly as returned by chores_list. Identifies the round being completed."
    • addedInput schema / properties / id / description
      Added value: +"Id of the chore, from chores_list."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description goes well beyond by disclosing the side effects (next due date scheduled from cadence, rotation to next non-absent member, open swap request closed) and the optimistic-concurrency rejection behavior. It also names the error codes and the response payload shape, which is valuable given there is no output schema. Minor gap: it does not state permission requirements or what happens if the caller is not the assigned member.

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 action, then prerequisites, then error handling, then exclusions and return shape — a logical order with no filler sentences. It is dense and runs as a single block, which slightly hurts scannability, but every sentence carries operational information.

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?

For a non-idempotent mutation with no output schema, the description covers side effects, error semantics, the return payload (updated chore plus completion with previous values), and the recovery path. Nothing an agent needs in order to call it correctly and handle failures 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 real meaning: the expected* parameters are concurrency guards sourced verbatim from chores_list, and the reason they exist (stale or double completion is rejected). That is semantic context the schema's per-field descriptions do not convey.

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 with scope: 'Mark the current round of a chore as done by the calling member.' It also explicitly separates itself from chore_update ('Not for editing a chore'), so an agent can distinguish it from the nearest sibling 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?

Gives an explicit prerequisite workflow (call chores_list first and pass nextDueAt/assignedMemberId), names the alternative for the editing case (chore_update), and prescribes behavior on the two named error outcomes, including an explicit 'do not retry blindly' instruction. It also points to chore_complete_undo for reversal, covering the when-not path.

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