Codecks MCP Server

codecks_create_space

Create a new space to organize decks within a Codecks project, helping structure game development workflows and task management.

Instructions

Create a new space in a project. Spaces are containers for organizing decks.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	The space name
`project`	No	Optional project name. Uses CODECKS_DEFAULT_PROJECT from config if not provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Feb 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral context. It states the action is creation but doesn't disclose permissions needed, whether it's idempotent, what happens on failure, or the response format. 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 front-loaded and concise with two sentences that directly state the purpose and resource context. Every sentence earns its place without redundancy or unnecessary details.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical context like error handling, return values, or behavioral traits (e.g., effects on existing data), which are essential for proper tool 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?

Schema description coverage is 100%, so the schema already documents both parameters ('name' and 'project'). The description adds no additional meaning beyond what's in the schema, such as constraints or examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 space') and resource ('in a project'), specifying that spaces are 'containers for organizing decks.' It distinguishes from siblings like 'codecks_create_project' or 'codecks_create_deck' by focusing on spaces, but doesn't explicitly differentiate beyond the resource type.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., needing an existing project), when not to use it (e.g., if a space already exists), or refer to sibling tools like 'codecks_list_spaces' for checking existing spaces.

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

Deploy Server