Skip to main content
Glama

Read one chore

chore_get
Read-onlyIdempotent

Fetches a single chore by ID and returns its schedule: title, interval days, recurrence type, next due date, and assigned member. Use it when the chore ID is already known.

Instructions

Fetch a single chore by id with its schedule (title, intervalDays, recurrenceType, nextDueAt, assignedMemberId). Use when you already know the id; use chores_list to find ids, see all chores, or read last completion data, which this tool does not include. Returns chore_not_found if the id is not a chore of this flat.

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_get"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / id / description
      Added value: +"Id of the chore, from chores_list."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: the tool is flat-scoped, it deliberately excludes last completion data, and it signals a specific 'chore_not_found' error. It stops short of describing permissions or whether the flat is resolved from wgCode versus the account, which is a minor remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the fetch-and-return-fields statement, followed by the disambiguation rule. The parenthetical field list is dense but every item earns its place given there is no output schema.

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?

With no output schema, the description compensates by enumerating the returned fields and calling out the excluded one (last completion data). Combined with the error case and the sibling routing, an agent has everything needed to call it correctly.

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 coverage is 100%, with both 'id' and 'wgCode' fully documented in the schema, so the baseline is 3. The description reinforces that the id comes from chores_list but says nothing about wgCode or how flat resolution behaves when it is omitted, adding little beyond 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?

States a specific verb and resource ('Fetch a single chore by id') and immediately enumerates the returned schedule fields, so the agent knows exactly what shape of data it gets back. It is clearly distinct from the sibling chores_list without needing to open 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?

Explicit condition for use ('when you already know the id') plus an explicit routing rule to chores_list for finding ids, listing all chores, and reading last completion data. It also names the 'chore_not_found' outcome when the id does not belong to the flat.

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