Agent Chef

Hide the setup checklist

dismiss_setup_checklist

Hides the 'Get set up' card on the household dashboard when the owner says they don't need it. Pass show=true to bring it back.

Instructions

Hides the 'Get set up' card on the household dashboard (e.g. when the owner says they don't need it). Pass show=true to bring it back.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dismiss_setup_checklist"
  }
}

Input Schema

Name	Required	Description	Default
`show`	No

Output Schema

Name	Required	Description	Default
`hidden`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the non-obvious fact that this 'dismiss' tool is actually a reversible toggle via show=true, which the name and annotations do not convey. It does not mention permission requirements for an owner-level dashboard change.

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 tight sentences: the action and target come first, the trigger example and the reversal follow. No filler, nothing restated from the schema or annotations.

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?

Output schema exists, so return values need no explanation, and annotations cover the safety profile. The description supplies purpose, trigger and reversal; only minor gaps remain, such as idempotency of repeated dismissal.

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 description coverage is 0% and the lone parameter 'show' is undocumented in the schema, so the description must carry the load. It does so by explaining that show=true restores the card, resolving the otherwise confusing boolean on a tool named 'dismiss'.

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: it hides the 'Get set up' card on the household dashboard. No sibling tool operates on the dashboard checklist, so the agent can immediately tell this apart from the recipe/voting/member tools.

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

Usage Guidelines4/5

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

Gives a concrete trigger scenario ('when the owner says they don't need it') and explicitly states how to reverse the action ('Pass show=true to bring it back'). It does not state when NOT to use it or name alternatives, but there are no competing siblings for this purpose.

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