Agent Chef

Add or edit a member

upsert_member

Destructive

Add or edit a household member's name, phone, email, and role. Update contact details without removing and re-adding, which breaks their vote link.

Instructions

Add a household member, or edit one: name is the key (case-insensitive), or pass member_id from get_members to rename. Phone and email update when given; an empty string clears them. Use this when someone wants to add or fix a member's contact details; never remove and re-add, which breaks their vote link. Roles: member (default) can vote, rate and browse once they sign in; admin can also change settings, recipes and weeks like the owner.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`role`	No	Only for members who have signed in to Agent Chef (has_account); admin needs an account
`email`	No	An empty string clears it.
`phone`	No	E.164, e.g. +15551234567. An empty string clears it.
`member_id`	No	Edit this member by id (from get_members); this is how you rename someone. Without it, name is the match key.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`role`	No	owner = primary owner; admin = runs the household like the owner; member = votes, rates and browses
`email`	No
`phone`	No
`vote_link`	No	Personal voting page for this member
`has_account`	No	True once this member has signed in to Agent Chef with their own account
`push_subscribed`	No	Has a device opted in to push notifications

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.1.1Oct 3, 2026

addedInput schema / properties / email / description
```
Added value: +"An empty string clears it."
```

addedInput schema / properties / member_id

Added value: +{
+  "description": "Edit this member by id (from get_members); this is how you rename someone. Without it, name is the match key.",
+  "type": "string"
+}

changedInput schema / properties / phone / description

Previous value: -"E.164, e.g. +15551234567"New value: +"E.164, e.g. +15551234567. An empty string clears it."

addedInput schema / properties / role

Added value: +{
+  "description": "Only for members who have signed in to Agent Chef (has_account); admin needs an account",
+  "enum": [
+    "admin",
+    "member"
+  ],
+  "type": "string"
+}

addedOutput schema / 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 / push_subscribed

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

changedOutput schema / 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 / 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

A4.5/5.0

Behavior4/5

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

Annotations supply destructiveHint=true and readOnlyHint=false; the description adds real behavioral detail beyond them — empty string clears phone/email, name is the case-insensitive match key, member_id is how you rename, and role capabilities (member vs admin). It doesn't state what happens on a name collision when adding or whether clears are reversible, so it's not a 5.

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?

Purpose and key semantics are front-loaded, and each sentence carries information (identity key, clear semantics, routing rule, role model). The final roles sentence is long but earns its place; overall it is dense without much waste.

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?

An output schema exists, so return values needn't be described. The description covers identity/rename mechanics, field clearing, and role implications for a 5-param mutation tool; only edge cases like name collisions or unauthorized role assignment are unaddressed.

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 80%, so the baseline is 3, but the description genuinely adds meaning: how name/member_id interact as the key, that empty strings clear contact fields, and what each role can do beyond the terse schema enum note.

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 opening clause states a precise compound verb+resource ('Add a household member, or edit one') and immediately defines the matching key (name, case-insensitive, or member_id). This lets an agent distinguish it from get_members and remove_member 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?

Explicit when-to-use ('when someone wants to add or fix a member's contact details') plus an explicit when-not/alternative: 'never remove and re-add, which breaks their vote link.' That is a concrete routing rule an agent can act on.

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