Skip to main content
Glama
kenzotp

mcp-server-zuuna

by kenzotp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zuuna_create_card

Create a card on a board with a required title, targeting a column by ID/title or the first column. Use an idempotency key to retry safely without duplicate cards.

Instructions

Create a card on a board. Title is required; give the target column by id or by title (omitted = the board's first column). Returns the new card's id and key. Retries are safe: pass the same idempotencyKey again after a lost response or 5xx and the API returns the original card instead of a duplicate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesCard title (required).
boardIdNoBoard id (from zuuna_boards). Provide this or boardKey.
boardKeyNoBoard key/title instead of boardId; resolved via the board list.
columnIdNoTarget column id. Provide this or columnTitle.
columnTitleNoTarget column title (resolved against the board's columns).
descriptionNoCard description (plain text or sanitized HTML). null clears.
idempotencyKeyNoClient-chosen key for safe retries (e.g. "order-4711-card"). If this key was already used in this workspace, the API returns the ORIGINAL card (200) instead of creating a duplicate. Use a fresh key for each new card; reuse one key only for retries of the same logical card.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It clearly discloses key non-obvious behavior: idempotency key retries return the original card instead of duplicating, and an omitted column defaults to the board's first column. It does not cover auth or permissions, but these are less critical for selection and invocation.

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 compact sentences with no filler. It front-loads the core creation statement and then packs the most important invocation and retry semantics into the second sentence.

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 7-parameter creation tool with no output schema, the description covers key invocation details: required title, column targeting, default column, return values, and retry safety. It does not explicitly state that boardId or boardKey is required, but the schema descriptions provide that 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 the baseline is 3. The description adds meaningful semantics beyond the schema, such as the column default behavior, the ability to target columns by id or title, and the idempotency contract. These details help the agent choose parameter values correctly.

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 and resource: 'Create a card on a board.' It also adds essential scope details such as requiring a title and targeting a column by id or title, which distinguishes it from sibling mutation tools like update_card and move_card.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the creation purpose obvious and provides operational guidance, but it does not explicitly state when to prefer this tool over siblings or when to use alternatives like update_card or move_card. Usage context is implied rather than explicitly framed as a decision.

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