Skip to main content
Glama

Edit a chore

chore_update

Edit an existing chore's title, assignee, due date, or repeat rhythm by sending only changed fields; pass expectedUpdatedAt to reject the edit if another member saved first.

Instructions

Change the title, assignee, next due date or rhythm of an existing chore; send only the fields to change. Use this to rename, reassign or reschedule. To record that the chore was done use chore_complete, which also rotates the assignee. Any member may edit. Handing a chore due within 24 hours to another member sends that member a push notification. Pass expectedUpdatedAt (the updatedAt from chore_get or chores_list) to reject the edit when someone else saved the chore since. Returns chore_not_found for an unknown id, member_not_in_wg for an assignee who is not an active member and chore_changed if the chore was changed by someone else in the meantime: read the chore again and retry. Returns the updated chore.

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>"
    },
    "name": "chore_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the chore, from chores_list.
titleNoNew name of the chore, e.g. "Bathroom". Omit to keep the current one.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
nextDueAtNoNew due date as ISO 8601 with offset. Omit to keep the current one.
intervalDaysNoNew repeat interval in days, or in months when the recurrenceType is months (then at most 60).
recurrenceTypeNoNew unit of intervalDays: days or months. Omit to keep the current one.
assignedMemberIdNoId of the new assignee, from members_list. Null removes the assignment; omit to keep it.
expectedUpdatedAtNoThe updatedAt of the chore as last read from chore_get or chores_list, ISO 8601 with offset. When set, the edit only applies if the chore is unchanged since; otherwise chore_changed. Omit to skip the check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / expectedUpdatedAt
      Added value: +{
      +  "description": "The updatedAt of the chore as last read from chore_get or chores_list, ISO 8601 with offset. When set, the edit only applies if the chore is unchanged since; otherwise chore_changed. Omit to skip the check.",
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +  "type": "string"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "New name of the chore, e.g. \"Bathroom\". Omit to keep the current one.",
      +  "maxLength": 120,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / assignedMemberId / description
      Added value: +"Id of the new assignee, from members_list. Null removes the assignment; omit to keep it."
    • addedInput schema / properties / id / description
      Added value: +"Id of the chore, from chores_list."
    • addedInput schema / properties / intervalDays / description
      Added value: +"New repeat interval in days, or in months when the recurrenceType is months (then at most 60)."
    • addedInput schema / properties / nextDueAt / description
      Added value: +"New due date as ISO 8601 with offset. Omit to keep the current one."
    • addedInput schema / properties / recurrenceType / description
      Added value: +"New unit of intervalDays: days or months. Omit to keep the current one."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which only say non-read-only, non-idempotent, non-destructive), the description discloses the permission model ("Any member may edit"), a side effect (push notification when handing off a chore due within 24 hours), the conflict-detection behavior of expectedUpdatedAt, and three concrete error codes with remediation. That is substantive behavior the structured fields do not carry.

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 mutation scope and the sibling disambiguation, then layered side effects and error handling. Dense but every sentence carries information; the single-paragraph form makes the error-code list slightly harder to scan than a structured list would.

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 an 8-parameter mutation tool with no output schema, the description covers return value ("Returns the updated chore"), permissions, notification side effects, concurrency semantics, and error taxonomy with recovery steps. An agent has enough to call this correctly on the first attempt.

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 schema already documents each field; the description still adds the cross-cutting semantic that only changed fields should be sent (omit-to-keep), which is not obvious from individual property descriptions. It also ties expectedUpdatedAt to the chore_changed outcome and the retry loop, though it does not elaborate on the intervalDays/recurrenceType interaction beyond what the schema says.

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?

Opens with a specific verb plus resource and enumerates exactly which fields are mutable (title, assignee, next due date, rhythm), then states the partial-update contract. It explicitly separates itself from the sibling chore_complete by naming that tool and its different effect (rotating the assignee).

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 explicit when-to-use framing ("rename, reassign or reschedule"), an explicit when-not with the alternative named ("To record that the chore was done use chore_complete"), and operational guidance on the optimistic concurrency parameter plus a retry procedure on chore_changed. Nothing about selecting this tool is left to inference.

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