Skip to main content
Glama

Read the cleaning rota

chores_list
Read-onlyIdempotent

Lists recurring flat chores by soonest due date with assignee, interval, history, and monthly completions so you can see who is due and get the assignee ID and due date needed to complete a chore.

Instructions

List every recurring chore of the flat, soonest nextDueAt first. Each chore carries assignedMemberId, intervalDays, recurrenceType, nextDueAt, lastCompletedAt and lastCompletedByName; the response also has monthCompletions (completions this month per member id). Use this to see who is due and as the required read before chore_complete, which needs nextDueAt and assignedMemberId from here. For a single chore use chore_get.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chores_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description goes beyond them by disclosing the response shape (assignedMemberId, intervalDays, recurrenceType, nextDueAt, lastCompletedAt, lastCompletedByName, plus monthCompletions per member) and the workflow dependency on chore_complete. That return-shape and dependency information is exactly the kind of context annotations cannot supply.

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?

Three sentences, front-loaded with purpose and ordering before the field enumeration, then the sibling pointer last. The middle field list is dense but each item is functional; no filler or repetition of the tool name.

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?

No output schema exists, so the description carries the return-value burden and does so by naming the key fields and monthCompletions. Combined with the sort order, the prerequisite chain, and the single-chore alternative, nothing an agent needs in order to call it correctly is missing.

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?

There is one optional parameter (wgCode) and schema description coverage is 100%, including its pattern and the "leave it out when the account belongs to one flat" default behavior. The description adds nothing about wgCode, so baseline 3 applies — the schema does all the work here.

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 ("List every recurring chore of the flat") plus the sort order ("soonest nextDueAt first"), and explicitly contrasts with the sibling chore_get for single-chore reads. An agent can distinguish this from chore_get and members_list without opening any 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 explicit when-to-use ("see who is due"), a hard prerequisite ("the required read before chore_complete, which needs nextDueAt and assignedMemberId from here"), and routes single-chore needs to chore_get. This is the when/when-not/alternative triad in compact form.

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