Codecks MCP Server

codecks_create_deck

Create a new deck in a Codecks project to organize tasks and workflows, with options to specify project and space placement.

Instructions

Create a new deck in a project, optionally in a specific space.

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": {
      "title": "<title>"
    },
    "name": "codecks_create_deck"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	The deck title
`project`	No	Optional project name. Uses CODECKS_DEFAULT_PROJECT from config if not provided.
`spaceId`	No	Optional space ID to create the deck in. Defaults to space 1 if not specified.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Feb 19, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the creation action without behavioral details. It doesn't disclose required permissions, whether creation is idempotent, error conditions, or what happens if the project/space doesn't exist. This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that front-loads the core purpose ('Create a new deck in a project') and adds optional context. Every word earns its place with zero redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what a 'deck' represents in this context, what happens on success/failure, or return values. Given the mutation nature and lack of structured data, more context is needed.

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%, so the schema fully documents all three parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., no format examples or constraints). Baseline 3 is appropriate when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a new deck') and resource ('in a project'), with additional context about optional space placement. It distinguishes from siblings like 'codecks_create_project' and 'codecks_create_space' by focusing on decks, though it doesn't explicitly contrast with 'codecks_update_deck'.

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 implies usage for creating decks within projects, with optional space specification. However, it lacks explicit guidance on when to use this versus alternatives like 'codecks_update_deck' for modifications or 'codecks_list_decks' for viewing. No prerequisites or exclusions are mentioned.

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

Deploy Server