Skip to main content
Glama
Sign In
Codecks MCP Server

Codecks MCP Server

by microkorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

codecks_create_card

Create a new task card in a Codecks project deck to track game development work items and manage workflows. Specify deck by ID or name with optional project for resolution.

Instructions

Create a new card in a deck. Specify either deckId or deckName (with optional project for name resolution).

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

Input Schema

NameRequiredDescriptionDefault
contentYesThe card content/title
deckIdNoThe deck ID to create the card in. Either deckId or deckName must be provided.
deckNameNoThe deck name to create the card in (resolved to ID internally). Either deckId or deckName must be provided.
projectNoProject name for deck name resolution. Uses default project if not specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 basic creation action. It doesn't disclose behavioral traits like whether this requires specific permissions, what happens on duplicate card names, if there are rate limits, or what the response format looks like. For a mutation tool with zero annotation coverage, this is insufficient.

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 and immediately provides parameter guidance. Every word earns its place with zero wasted text or 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 mutation tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after creation, potential error conditions, or how this tool differs behaviorally from similar siblings like update_card. The schema handles parameter documentation, but the description lacks crucial operational context.

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 all 4 parameters thoroughly. The description adds minimal value by mentioning the either/or relationship between deckId and deckName and the optional project parameter, but doesn't provide additional semantics beyond what's in the schema descriptions.

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 card') and target resource ('in a deck'), distinguishing it from siblings like create_deck or create_project. However, it doesn't explicitly differentiate from update_card or move_card in terms of creation versus modification operations.

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 clear context for parameter usage ('Specify either deckId or deckName'), but lacks explicit guidance on when to use this tool versus alternatives like update_card for existing cards or move_card for relocation. It mentions optional project usage but doesn't compare with other creation tools.

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