Skip to main content
Glama
Sign In
Fizzy MCP Server

Fizzy MCP Server

by Fabric-Pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Column

fizzy_delete_column
Destructive

Permanently delete a workflow column from a board. Cards in the column are moved to triage to keep them safe.

Instructions

Permanently delete a workflow column from a board. Cards in this column will be moved to triage. ⚠️ This is a destructive operation that cannot be undone.

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>",
      "column_id": "<column_id>"
    },
    "name": "fizzy_delete_column"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_idYesThe unique board identifier: a 25-character identifier, e.g., '0000000000000000000000abc'. Get available board IDs from fizzy_get_boards.
column_idYesThe unique column identifier: a 25-character identifier, e.g., '0000000000000000000000abc'. Columns represent workflow stages. Get available column IDs from fizzy_get_columns.
account_slugYesThe 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.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior5/5

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

While the annotations already set destructiveHint to true, the description adds concrete behavioral detail beyond that flag: it explains that cards in the column will be moved to triage and that the operation 'cannot be undone.' This gives an agent a clear picture of the side effects and permanence, which is exactly the kind of context destructive operations need.

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?

The description is three terse sentences: the core action, the side effect, and the explicit warning about irreversibility. Every sentence contributes needed information and the most important fact is front-loaded, with no filler or redundancy.

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?

All three required parameters are fully documented in the schema, the annotations mark the operation destructive, and the description adds the crucial behavioral consequence of moving cards to triage and irreversible deletion. For a delete operation with this level of schema and annotation support, an agent has enough information to correctly select and invoke the tool.

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?

The schema descriptions already cover 100% of the parameters, providing examples and telling the agent where to obtain valid IDs from sibling tools like fizzy_get_boards, fizzy_get_columns, and fizzy_get_identity. The tool description itself adds no parameter-level details, but because the schema is rich, the baseline score of 3 is appropriate.

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 begins with 'Permanently delete a workflow column from a board,' which names the specific verb, target resource, and scope. The added consequence that cards are moved to triage further clarifies what this operation does and distinguishes it from sibling deletion tools like fizzy_delete_board, fizzy_delete_card, and fizzy_delete_comment.

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 description clearly implies the intended use case—deleting a workflow column—but does not explicitly state when to use it versus alternatives or when not to use it. It does note the behavioral consequence (cards moved to triage), which gives helpful context, but it never references sibling tools such as fizzy_update_column or fizzy_move_card_to_column.

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

Deploy Server

Other Tools