Fizzy MCP Server

Delete Board

fizzy_delete_board

Destructive

Permanently remove a project board and all associated cards, columns, and data. This destructive action cannot be undone, so use it only when certain.

Instructions

Permanently delete a board and all its contents including cards, columns, and associated data. ⚠️ This is a destructive operation that cannot be undone. Use with caution.

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": {
      "account_slug": "<account_slug>",
      "board_id": "<board_id>"
    },
    "name": "fizzy_delete_board"
  }
}

Input Schema

Name	Required	Description	Default
`board_id`	Yes	The unique board identifier: a 25-character identifier, e.g., '0000000000000000000000abc'. Get available board IDs from fizzy_get_boards.
`account_slug`	Yes	The account slug identifier (e.g., '123456' or '/123456'). This identifies which Fizzy account to operate on. Get available account slugs from fizzy_get_identity or fizzy_get_accounts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Sep 5, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already mark the operation as destructive, and the description adds valuable detail beyond that: it explicitly says the deletion cannot be undone and enumerates what will be destroyed (cards, columns, associated data). This gives an agent a clear mental model of the operation's consequences.

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?

The description is short and front-loaded, with the destructive scope stated in the first sentence. 'Use with caution' is mildly redundant after 'cannot be undone,' but overall the text is tight and effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple destructive action with two fully documented parameters, the description provides all essential context: the operation is permanent, widespread in scope, and should be treated carefully. No output schema exists, but for a delete operation this omission is not a meaningful gap.

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 100% and the schema itself provides detailed parameter descriptions, including formats, examples, and how to obtain valid values via fizzy_get_boards, fizzy_get_identity, or fizzy_get_accounts. The description adds no new parameter-level semantics, so the baseline of 3 applies.

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?

The description uses a specific verb/resource pair — 'Permanently delete a board' — and expands on scope by naming what is removed: cards, columns, and associated data. This clearly distinguishes it from sibling delete tools such as fizzy_delete_card or fizzy_delete_column.

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

Usage Guidelines3/5

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

The intended use is implied: choose this when you want to permanently remove an entire board. However, the description does not explicitly state when to use it versus alternatives, nor does it mention exclusions such as preserving any of the board's contents.

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

Deploy Server