Ferret

Mark a recall

set_recall_status

Idempotent

Update a household recall to dismissed, done, or open using its id from list_recalls, so resolved items leave the needs-attention list and dismissed ones are marked not affected.

Instructions

Marks a recall on one of the household's things, once the person says: dismissed (not theirs — a different model), done (dealt with: repaired, refunded, replaced) or open (again). The id comes from list_recalls. Dismissed and done ones leave what_needs_attention.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "status": "<status>"
    },
    "name": "set_recall_status"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The recall match's id, from list_recalls
`status`	Yes	dismissed: not affected; done: dealt with; open: needs dealing with again

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2026.11.6Nov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world, so the bar is lower; the description still contributes a genuine side effect — dismissed and done recall matches drop out of what_needs_attention — which is behavioral context the annotations do not encode.

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 sentences, front-loaded with the action, then the trigger conditions, then the id source. The parenthetical glosses are information-dense rather than padding, and nothing is repeated from the schema verbatim.

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 two-parameter mutation with full enum documentation and an idempotency annotation, the description covers purpose, triggers, id provenance, and downstream effect. It omits only the response shape, which is not supplied as an output schema, so a minor gap.

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 100% and both params are documented, so the baseline is 3; the description earns a point by mapping each enum value to a real-world situation and stating where the id comes from, adding meaning beyond the enum strings themselves.

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 (marks a recall status on a household item) and immediately enumerates the three terminal states with plain-language meanings, so an agent can tell it apart from list_recalls (read) and what_needs_attention (aggregate view).

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 concrete triggers for each status — dismissed for a different model, done for repaired/refunded/replaced, open to re-raise — and names list_recalls as the id source. It stops short of saying when not to use this tool (e.g., that new recalls cannot be created here) or what happens if the status is already set, but the routing guidance is strong.

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