Fizzy MCP Server

List Boards

fizzy_get_boards

Read-only

Retrieve all boards in a Fizzy account to discover available board IDs, names, descriptions, and URLs before managing cards. Returns the complete list in one request with no pagination.

Instructions

Get all boards in a Fizzy account. Returns board details including IDs, names, descriptions, and URLs. Use this to discover available boards before working with cards. The result is the complete list: every upstream page is fetched server-side, so there is no page parameter and nothing further to request.

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

Input Schema

Name	Required	Description	Default
`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.3/5.0

Behavior4/5

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

With annotations already declaring readOnlyHint=true and destructiveHint=false, the description adds meaningful behavioral context: every upstream page is fetched server-side, there is no page parameter, and the result is a complete list. This goes beyond the annotations to set correct pagination expectations, though it omits rate-limit or performance details.

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 sentences, each serving a distinct purpose: defining scope, listing return fields, and clarifying pagination behavior. Front-loaded and no filler; every sentence earns its place.

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 read-only list tool with one fully documented parameter and no output schema, the description covers scope, return fields, usage context, and completeness of results. Nothing an agent needs to invoke it correctly is missing.

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 provides 100% coverage for the single parameter account_slug, including format examples and where to obtain valid values. The description does not add parameter-specific meaning beyond the schema, 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?

States a specific verb and resource ('Get all boards in a Fizzy account') and lists the returned fields (IDs, names, descriptions, URLs). The plural 'all' clearly differentiates it from the sibling fizzy_get_board, and the title 'List Boards' reinforces the intent.

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?

Explicitly instructs when to use this tool: 'discover available boards before working with cards.' This gives clear context for selection. It does not explicitly name alternatives like fizzy_get_board for single-board lookups, so it stops short of a 5.

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

Deploy Server