Fizzy MCP Server

Close Card

fizzy_close_card

Close a card and archive it to mark work as done, removing it from active board view. Use when a task is completed and needs to be cleared from the current workflow.

Instructions

Close a card to mark it as done/completed. Closed cards are archived and removed from active view. Use this when work on a card is finished.

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>",
      "card_number": "<card_number>"
    },
    "name": "fizzy_close_card"
  }
}

Input Schema

Name	Required	Description	Default
`card_number`	Yes	The card number - the visible ID shown on the board (e.g., '#123'). This is different from card_id and is used for some endpoints. Card numbers are shown in the Fizzy UI and are user-friendly identifiers.
`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?

The description adds behavior beyond the annotations by stating that closed cards are 'archived and removed from active view'. This clarifies the tool's side effects in a way the readOnlyHint and destructiveHint do not fully capture. It does not contradict the annotations, since 'archived' implies retention rather than destruction.

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 two concise sentences with no unnecessary words. It leads with the core action and result, then provides usage context. Every sentence earns its place.

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 mutation tool with no output schema, the description covers the core behavior, result, and when to use it. It does not mention reversibility or relationship to fizzy_reopen_card, but the core information an agent needs to select and call it is present.

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%, and both 'account_slug' and 'card_numbr' have detailed descriptions in the schema. The tool description does not add parameter-specific semantics, so the baseline 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 states a specific verb ('Close'), a resource ('a card'), and the resulting state ('mark it as done/completed', 'archived and removed from active view'). This clearly distinguishes the action from sibling tools like fizzy_delete_card and fizzy_reopen_card.

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?

The description gives an explicit trigger condition: 'Use this when work on a card is finished.' This provides clear context for when to invoke the tool, though it does not explicitly mention alternatives or state when not to use it, such as when deletion is intended.

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

Deploy Server