Skip to main content
Glama
coryshaw

Agent Chef

by coryshaw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Add candidates to the ballot

add_candidates

Append extra recipes to the current voting ballot to address feedback, keeping existing votes and alerting voters via message_group.

Instructions

Append extra recipes to the current voting ballot (positions continue after the existing ones; votes are kept; 15 max). Use in response to ballot_feedback from get_current_week; open feedback is marked addressed. Follow up with message_group so voters know new options are up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recipesYes
week_idNo
addresses_feedbackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
weekYes
addedYes
similarYesNew recipes that closely resemble one the household already has; consider using theirs
feedbackYes
replacedYesNew recipes swapped for the household's own version of the same dish; the existing recipe is on the ballot instead
candidatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.1.1
    • changedInput schema / properties / recipes / items / properties / image_url / description
      Previous value: -"A real, publicly reachable photo of the dish: the og:image of the recipe page you used, or one found via web/image search. The server verifies the URL is an image and drops it otherwise. Never invent URLs; prefer import_recipe, which captures the source photo."New value: +"A real, publicly reachable photo of the dish: the og:image of the recipe page you used, or one found via web/image search. The server verifies the URL is an image and drops it otherwise. Never invent URLs; prefer import_recipe, which captures the source photo. For generated images use set_recipe_image afterwards."
    • addedOutput schema / properties / added / items / properties / admin_pick
      Added value: +{
+  "description": "Selected even though the vote alone would not have picked it: chosen by an admin, or added off the ballot",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • addedOutput schema / properties / added / items / properties / image_generated
      Added value: +{
+  "description": "Photo was generated by Agent Chef, so it is safe to show publicly",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • addedOutput schema / properties / added / items / properties / is_public
      Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • addedOutput schema / properties / added / items / properties / public_url
      Added value: +{
+  "description": "Indexable public page, when published",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / added / items / properties / source_recipe_id
      Added value: +{
+  "description": "Set when this is the household's copy of a Community recipe",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / replaced
      Added value: +{
+  "description": "New recipes swapped for the household's own version of the same dish; the existing recipe is on the ballot instead",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "existing_title": {
+        "$ref": "#/properties/week/properties/id"
+      },
+      "recipe_id": {
+        "$ref": "#/properties/week/properties/id"
+      },
+      "title": {
+        "$ref": "#/properties/week/properties/id"
+      }
+    },
+    "required": [
+      "title",
+      "recipe_id",
+      "existing_title"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / similar
      Added value: +{
+  "description": "New recipes that closely resemble one the household already has; consider using theirs",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "recipe_id": {
+        "$ref": "#/properties/week/properties/id"
+      },
+      "similar_to": {
+        "items": {
+          "additionalProperties": true,
+          "properties": {
+            "recipe_id": {
+              "$ref": "#/properties/week/properties/id"
+            },
+            "title": {
+              "$ref": "#/properties/week/properties/id"
+            }
+          },
+          "required": [
+            "recipe_id",
+            "title"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "title": {
+        "$ref": "#/properties/week/properties/id"
+      }
+    },
+    "required": [
+      "recipe_id",
+      "title",
+      "similar_to"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / week / properties / share_url
      Added value: +{
+  "description": "Public page showing this week's winners",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / required
      Previous value: -[
-  "week",
-  "added",
-  "candidates",
-  "feedback"
-]New value: +[
+  "week",
+  "added",
+  "replaced",
+  "similar",
+  "candidates",
+  "feedback"
+]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and the description adds real behavioral detail beyond them: votes are preserved, positions are appended rather than replacing, a 15-item cap applies, and open feedback is marked addressed as a side effect. The 15 max and the feedback mutation are the meaningful additions; it still doesn't state failure modes when the cap is exceeded.

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 the core action, then the behavioral constraint, then the trigger, then the follow-up — no filler sentences. Slightly dense with parentheticals but every clause carries information an agent needs.

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?

For a mutation tool with an output schema and annotations, the description covers the effect, the cap, the trigger, and the required next step, which is nearly everything needed to call it correctly. The only real gap is the unexplained week_id parameter.

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?

Top-level schema coverage is reported as 0% for recipes, week_id, and addresses_feedback. The description compensates partially by implying addresses_feedback semantics ('open feedback is marked addressed') and the append/15-max constraint on recipes, but week_id is never explained, so the schema gap is not fully closed.

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 ('Append') and resource ('extra recipes to the current voting ballot'), and the parenthetical clarifies the exact effect on the ballot (positions continue, votes kept). An agent can distinguish this from siblings like propose_recipes or add_vote without opening the 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?

Explicitly names the trigger condition ('in response to ballot_feedback from get_current_week') and the required follow-up ('Follow up with message_group'), routing the agent to the correct sibling both before and after invocation. This is precise when/when-not guidance grounded in named tools.

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

Deploy Server

Other Tools