Skip to main content
Glama
davegomez

fizzy-mcp

by davegomez
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

fizzy_step

Create, complete, update, uncomplete, or delete a step on a card by supplying content or index to match.

Instructions

Create, complete, update, uncomplete, or delete a step on a card.

Mode detection:

  • step absent → CREATE (requires content)

  • step present, no other params → COMPLETE (default action)

  • step + content → UPDATE content

  • step + completed: false → UNCOMPLETE

  • step + delete: true → DELETE

Arguments:

  • account_slug (optional): Uses session default if omitted

  • card_number (required): Card number containing the step

  • step (optional): Content substring to match OR 1-based index to identify existing step

  • content (optional): Step text for create or update

  • completed (optional): Set completion state (true or false)

  • delete (optional): Delete the step

Returns: JSON with step id, content, completed status.

Examples:

  • Create: {card_number: 42, content: "Write tests"}

  • Complete: {card_number: 42, step: "Write tests"}

  • Uncomplete: {card_number: 42, step: 1, completed: false}

  • Update: {card_number: 42, step: 1, content: "Write unit tests"}

  • Delete: {card_number: 42, step: "Write tests", delete: true}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_slugNoAccount slug. Uses default if omitted.
card_numberYesCard number containing the step.
stepNoStep to act on: content substring or 1-based index. Omit to create.
contentNoStep text for create or update.
completedNoSet completion state.
deleteNoDelete the step.

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it explains modes, parameter interactions, optionality, and return format. There are no contradictions, and the agent understands side effects (e.g., deletion is described).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with headings and bullet points, front-loading the purpose. It is somewhat lengthy due to comprehensive coverage, but every sentence adds value; minor trimming could improve conciseness.

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?

Given 6 parameters (1 required), no output schema, and no annotations, the description is thorough: it covers all modes, parameter semantics, and return values. An agent can use this tool correctly without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds substantial value beyond the schema by explaining the mode detection logic, how 'step' can be a substring or index, and how parameters combine. This aids correct invocation.

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 clearly states the tool's purpose: 'Create, complete, update, uncomplete, or delete a step on a card.' It uses specific verbs and a resource (step on a card), and the sibling tool names (e.g., fizzy_boards, fizzy_get_card) confirm it is distinct.

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 provides explicit mode detection logic and examples for each action, guiding when to use which parameters. It does not explicitly contrast with siblings, but the sibling names and context make the tool's domain clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davegomez/fizzy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server