Skip to main content
Glama

Ask the flat to take over a chore

chore_swap_request

Post a swap request for a chore to your flat noticeboard and notify other members when you cannot complete it, so someone else can take over.

Instructions

Posts a swap request for one chore to the flat noticeboard as the signed-in member and sends a push notification to the other members; it differs from note_create in that the post is tied to the chore. Use it when you cannot do a chore and want someone else to take it; for a general message use note_create. Only one open swap request exists per chore: if one is already open, nothing new is posted and the existing post is returned with duplicate true. The request closes automatically when the chore is reassigned with chore_update or completed with chore_complete, or by hand with note_update. An unknown choreId is not rejected: the post is then stored as an ordinary manual post. The answer holds the announcement and a warning when the push delivery could not be confirmed.

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": {
      "choreId": "<choreId>",
      "content": "<content>"
    },
    "name": "chore_swap_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoType of the post. Defaults to request, which stays on the board until resolved; info and decision fade from the board after 30 days.request
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
choreIdYesId of the chore to swap, from chores_list.
contentYesText of the request, for example why you cannot do the chore. Shown as written on the noticeboard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), it discloses duplicate handling with the returned duplicate flag, automatic closure triggers, the silent fallback to an ordinary manual post for unknown choreIds, and a warning field when push delivery is unconfirmed. That is exactly the non-obvious behavior an agent cannot infer from annotations or schema.

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 purpose and sibling differentiation, then edges cases. It is dense and a few clauses are packed into long sentences (duplicate handling, closure, fallback, warning), but no sentence is filler.

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?

Although there is no output schema, the description covers the response shape (the announcement plus a warning, and duplicate true on an existing open request), the idempotency-like duplicate rule, and lifecycle termination. Nothing an agent needs to call this safely 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 about choreId: an unknown id is not rejected but degrades to a manual post. It also characterizes content as being shown verbatim on the noticeboard. The kind and wgCode semantics are left entirely to the schema.

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 opens with a specific verb and resource ('Posts a swap request for one chore to the flat noticeboard') and immediately names the sibling it differs from, note_create, explaining the distinguishing property (the post is tied to the chore). An agent can separate this from note_create without opening either 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 triggering condition ('when you cannot do a chore and want someone else to take it') and an explicit exclusion with the alternative ('for a general message use note_create'). It also names the closing paths (chore_update, chore_complete, note_update), so the agent knows the full lifecycle.

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