Codecks MCP Server

codecks_update_deck

Rename a deck by updating its title in Codecks project management. Provide the deck ID and new title to modify deck names for organizing game development workflows.

Instructions

Rename a deck by updating its title.

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

Input Schema

Name	Required	Description	Default
`deckId`	Yes	The deck ID to rename
`title`	Yes	The new deck title

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool renames a deck, implying a mutation, but does not describe permissions required, whether changes are reversible, rate limits, or what the response looks like. This leaves significant gaps 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 with zero waste. It is front-loaded with the core action ('Rename a deck') and avoids unnecessary details, making it highly concise and well-structured.

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 the tool's complexity as a mutation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, reversibility), usage context, and output expectations, which are critical for safe and effective 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%, with both parameters (deckId and title) clearly documented in the schema. The description adds minimal value beyond the schema by implying the purpose of renaming, but does not provide additional context like format constraints or examples. Baseline 3 is appropriate when the 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 verb ('Rename') and resource ('a deck'), specifying the action of updating its title. It distinguishes from siblings like codecks_create_deck (creation) and codecks_list_decks (listing), but does not explicitly differentiate from codecks_update_card, which updates cards rather than decks.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing an existing deck), exclusions (e.g., not for creating or deleting decks), or direct comparisons to siblings like codecks_rename_space (for spaces) or codecks_update_card (for cards).

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

Deploy Server