add_candidatesAppend 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.
| Name | Required | Description | Default |
|---|---|---|---|
| recipes | Yes | ||
| week_id | No | ||
| addresses_feedback | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does so well: it discloses that positions continue, votes are kept, there is a 15-item max, and open feedback is marked addressed. These are valuable side effects beyond the basic 'append' action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three dense, purposeful sentences: core behavior first, then trigger, then follow-up. Every sentence earns its place with no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Strong coverage of trigger, side effects, limits, and orchestration with message_group. Minor gaps remain around top-level parameter semantics and return/acknowledgment details, but the description is largely sufficient for an agent to use it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Top-level schema description coverage is 0%, and the description only hints at recipes without explaining week_id or addresses_feedback. The nested recipe schema is detailed, but the top-level parameters are left undocumented in both schema and description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb 'Append' and a clear resource 'extra recipes to the current voting ballot', with behavioral details like positions continuing and votes kept. This distinguishes it from siblings like set_this_weeks_recipes or propose_recipes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit trigger context: 'Use in response to ballot_feedback from get_current_week' and a required follow-up with message_group. It does not name alternatives or state when not to use it, but the context is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a distinct resource and action, with detailed descriptions that clarify boundaries. The main confusable pair is run_agent_chef vs next_actions, which both return the due-action checklist and operating instructions, differing only by trigger context. propose_recipes vs add_candidates are also related but clearly separated by phase (initiating a cycle vs appending during feedback).
The overwhelming majority follow a verb_noun snake_case pattern (get_, update_, set_, add_, record_, remove_), which is highly predictable. Minor deviations include next_actions being a bare noun phrase rather than get_next_actions, and favorite_recipe using 'favorite' as a verb instead of something like toggle_favorite.
At 34 tools, the surface is heavy for an agent to select from, exceeding the 25+ threshold for 'too many'. The domain is genuinely broad, but several utility and meta tools (dismiss_setup_checklist, record_schedule, get_connected_agents, get_instructions) and overlapping entry points (run_agent_chef, next_actions) inflate the count and could be consolidated without losing capability.
The full weekly lifecycle is covered end-to-end: propose, vote, feedback, add candidates, lock in, shop, order, cook, rate, and mark done. Recipe, member, ingredient, and preference management all have solid get/update/create coverage. Minor gaps include no way to delete a recipe, remove a candidate from an active ballot, or cancel a week beyond reopen_voting, but these are work-aroundable and don't create dead ends.