Fizzy MCP Server

Update Column

fizzy_update_column

Update a workflow column's name or color to refine project stages or improve visual organization, without affecting existing cards.

Instructions

Update a workflow column's name or color. Use this to refine your workflow stages or improve visual organization. This does not affect cards in the column.

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_update_column"
  }
}

Input Schema

Name	Required	Description
`name`	No	The new name of the column
`color`	No	Visual color for the workflow column. Available colors: blue (default), gray (neutral), tan (warm), yellow (attention), lime (success), aqua (info), violet (creative), purple (priority), pink (highlight). Colors help visually organize and distinguish workflow stages.
`board_id`	Yes	The unique board identifier: a 25-character identifier, e.g., '0000000000000000000000abc'. Get available board IDs from fizzy_get_boards.
`column_id`	Yes	The unique column identifier: a 25-character identifier, e.g., '0000000000000000000000abc'. Columns represent workflow stages. Get available column IDs from fizzy_get_columns.
`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

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds a meaningful behavioral guarantee ('This does not affect cards in the column') beyond the structured metadata. It does not cover permissions or response details, but for a rename/recolor operation this is acceptable.

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 with no redundant wording. The action and scope are front-loaded, and each sentence contributes meaningful information.

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 simple update operation with fully documented parameters and ID-source references in the schema, the description is largely complete. The only minor gap is not stating that at least one of name or color should be supplied, but this is unlikely to block correct invocation.

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 description coverage is 100%, so the schema already thoroughly documents all five parameters. The description only restates name/color at a high level and adds no parameter-level detail beyond the schema.

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 names a specific verb and resource ('Update a workflow column's name or color') and immediately separates this tool from create/delete/get-column siblings. It also states a concrete non-effect, making the tool's scope unambiguous.

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?

Provides clear usage context: 'Use this to refine your workflow stages or improve visual organization' and notes it 'does not affect cards,' which implies card-moving actions belong elsewhere. It does not explicitly name an alternative tool, but no sibling provides column updating, so the guidance is sufficient.

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

Deploy Server