Frostbyte

whats_next_dismiss

Idempotent

Personally dismiss a task recommendation or release suggestion when the user asks. Does not dismiss a Signal or change project work. Use the target ID from whats_next.

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": {
      "projectId": "<projectId>",
      "kind": "<kind>",
      "targetId": "<targetId>",
      "context": "<context>"
    },
    "name": "whats_next_dismiss"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`targetId`	Yes
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.2/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 idempotentHint=true, so the safety profile is supplied. The description still adds real value by clarifying that dismissal is personal ('Personally') and that it 'does not change project work', which tells the agent the underlying task or release entity is untouched. It stops short of saying the dismissal can later be undone via whats_next_restore.

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?

Three short sentences, front-loaded with the action and scope, then the exclusion, then the prerequisite. No filler or restated name/title beyond what is needed to disambiguate.

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 four-parameter, non-destructive mutation with no output schema, the description covers purpose, sibling exclusion, and ID sourcing adequately. The missing piece is the recovery/undo story (whats_next_restore) and how projectId scopes the dismissal, which an agent would still need to infer.

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?

Schema coverage is only 25% — the context parameter is fully documented inline while projectId, targetId and kind carry no schema description. The description partially compensates: it explains where targetId comes from ('from whats_next') and its task/release wording maps onto the kind enum. projectId and the personal-vs-shared semantics of the dismissal remain unexplained.

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 ('dismiss') and precise resource ('a task recommendation or release suggestion'), and immediately scopes it against the lookalike operation by saying it 'Does not dismiss a Signal'. An agent can distinguish this from signals_dismiss and the delete_* siblings 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 Guidelines4/5

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

Gives an explicit trigger ('when the user asks') plus a negative exclusion ('Does not dismiss a Signal'), which implicitly routes to signals_dismiss. 'Use the target ID from whats_next' establishes the required upstream call. The one gap is that it never mentions whats_next_restore as the undo path for this reversible action.

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

All Frostbyte tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?