Agent Chef

Get household members

get_members

Read-only

List household members with contact details, account sign-in status, push notification settings, and personal voting links for weekly meal planning votes.

Instructions

List household members with contact info, whether they have signed in to Agent Chef themselves (has_account), whether they get push notifications, and their personal vote links.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Oct 3, 2026

addedOutput schema / properties / items / items / properties / has_account

Added value: +{
+  "description": "True once this member has signed in to Agent Chef with their own account",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / items / items / properties / push_subscribed

Added value: +{
+  "description": "Has a device opted in to push notifications",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

changedOutput schema / properties / items / items / properties / role / anyOf

Previous value: -[
-  {
-    "enum": [
-      "owner",
-      "member"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "owner",
+      "admin",
+      "member"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / items / items / properties / role / description

Added value: +"owner = primary owner; admin = runs the household like the owner; member = votes, rates and browses"

First observedv0.1.0Sep 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful shape about what comes back (has_account, push notification status, personal vote links), but no pagination, ordering, or auth context beyond that. Moderate added value on top of the annotations.

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?

A single front-loaded sentence that leads with the verb and resource before listing the returned fields. There is some redundancy in enumerating return values when an output schema exists, but it is compact and wastes no space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, an output schema present, and simple read semantics backed by annotations, the description is nearly sufficient. Return values are already specified by the output schema, so restating them is harmless but not required; no critical gap remains for an agent to call this correctly.

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?

The tool takes zero parameters, so there is nothing for the description to clarify. Baseline 4 applies: no parameter documentation is needed and none is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('List household members') and even enumerates the returned fields (contact info, has_account, push notification status, vote links). The resource is clearly distinct from sibling tools like get_connected_agents or upsert_member, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use, when-not-to-use, or named alternative is given. For a parameter-less read-all tool the intended usage is strongly implied by 'List household members', but nothing tells the agent to prefer this over, say, get_connected_agents when it wants account-level info.

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