Skip to main content
Glama
Sign In
Fizzy MCP Server

Fizzy MCP Server

by Fabric-Pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Gild Card

fizzy_gild_card

Mark a card as golden to flag high-priority work items. Golden cards get highlighted and can be filtered using indexed_by='golden' for quick access.

Instructions

Mark a card as golden (priority/important). Golden cards are highlighted and can be filtered using indexed_by='golden' in fizzy_get_cards. Use this to flag high-priority work items.

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

Input Schema

NameRequiredDescriptionDefault
card_numberYesThe 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_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.2/5.0
Behavior4/5

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

Annotations already indicate this is a non-read-only, non-destructive mutation, and the description adds meaningful behavioral context: golden cards are highlighted and become filterable via indexed_by='golden'. This goes beyond the structured annotations by describing the persistent effect of the action. It doesn't mention idempotency or the reverse operation, but the core behavior is transparent.

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 sentences with no wasted words. The core action is first, followed by the useful consequence and a concrete usage recommendation. 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 two-parameter mutation with robust schema descriptions and non-destructive annotations, the description covers what the tool does, why it matters, and how it interacts with another tool. It lacks only minor details such as behavior when a card is already gilded, but nothing critical is missing for 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?

The input schema already provides 100% coverage with detailed descriptions for both account_slug and card_number, including the distinction between card_number and card_id. The tool description adds no parameter-level meaning beyond that, so the baseline score 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 and resource: 'Mark a card as golden (priority/important).' It clearly explains what the operation does, differentiates the card's golden state from normal cards, and connects it to the filtering capability in fizzy_get_cards. This is unambiguous and distinct from the sibling tools.

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 clear usage context: 'Use this to flag high-priority work items.' It explains the practical effect (highlighting and filtering) but does not explicitly state when not to use it or mention the alternative ungild_card. Still, the guidance is sufficient for an agent to understand when this tool is appropriate.

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