Skip to main content
Glama

Create a chore

chore_create

Create a recurring chore with a repeat interval, first due date, and optional assignee; notifies the assigned member when it is due within 24 hours.

Instructions

Create a new recurring chore in the flat. Use for a task that repeats on a fixed rhythm; to mark an existing chore as done use chore_complete, and to change an existing chore use chore_update. If nextDueAt is omitted the first due date is one interval from now. A chore assigned to another member that is due within 24 hours sends that member a push notification; self-assignment does not. An assignee who is not an active member fails with member_not_in_wg. Returns the created 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": {
      "title": "<title>"
    },
    "name": "chore_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort name of the chore, e.g. "Bathroom".
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
nextDueAtNoFirst due date as ISO 8601 with offset, e.g. 2026-12-01T18:00:00+01:00. Defaults to one interval from now.
intervalDaysNoRepeat interval. Counts days, or months when recurrenceType is months (then at most 60). Defaults to 7.
recurrenceTypeNoUnit of intervalDays: days (default) or months. Months keep the same day of the month.
assignedMemberIdNoId of the member who does the first round, from members_list. Omit or null for no assignee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / assignedMemberId / description
      Added value: +"Id of the member who does the first round, from members_list. Omit or null for no assignee."
    • addedInput schema / properties / intervalDays / description
      Added value: +"Repeat interval. Counts days, or months when recurrenceType is months (then at most 60). Defaults to 7."
    • addedInput schema / properties / nextDueAt / description
      Added value: +"First due date as ISO 8601 with offset, e.g. 2026-12-01T18:00:00+01:00. Defaults to one interval from now."
    • addedInput schema / properties / recurrenceType / description
      Added value: +"Unit of intervalDays: days (default) or months. Months keep the same day of the month."
    • addedInput schema / properties / title / description
      Added value: +"Short name of the chore, e.g. \"Bathroom\"."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=false, destructive=false), the description discloses the default due date computation, the side effect of sending a push notification when a chore is assigned to another member and due within 24 hours (with the self-assignment exclusion), and a concrete failure mode (member_not_in_wg). It stops short of stating whether the notification is suppressed on updates or how the returned chore is shaped, but the notification disclosure is exactly the kind of non-obvious effect that matters for a create call.

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?

Four sentences, each carrying distinct information (purpose, alternatives, default due date, notification/error behavior, return value), with the core purpose front-loaded. A minor redundancy is re-stating the nextDueAt default that the schema already documents.

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 six-parameter creation tool with no output schema, the description covers defaults, side effects, failure conditions, and the return value, which is everything an agent needs before calling. Nothing material is left to inference.

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 every parameter is already documented in the schema, including the nextDueAt default and the months-mode interval cap. The description restates the nextDueAt default but adds no semantics the schema lacks, so the baseline 3 applies.

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 first sentence gives a specific verb and resource ("Create a new recurring chore in the flat") and immediately distinguishes this from chore_complete and chore_update by naming both siblings and what they do instead. An agent can route correctly without opening any other 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?

It states the positive case (a task repeating on a fixed rhythm) and explicitly redirects the two adjacent cases: marking done goes to chore_complete, modifying goes to chore_update. That is explicit when-to-use and when-not-to-use with named alternatives.

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