basecamp_move_kanban_cardRelocate a kanban card to a specified column and position within your Basecamp project board.
Move a kanban card to a different column and/or position within that column.
| Name | Required | Description | Default |
|---|---|---|---|
| card_id | Yes | Basecamp resource identifier | |
| column_id | Yes | ||
| position | No | 1-indexed position within the destination column (1 = top). If not specified, the card is added to the top of the column. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.2.1Input schema / properties / bucket_idRemoved value: -{
- "description": "Basecamp resource identifier",
- "type": "number"
-}Input schema / properties / card_id / $refRemoved value: -"#/properties/bucket_id"Input schema / properties / card_id / descriptionAdded value: +"Basecamp resource identifier"Input schema / properties / card_id / typeAdded value: +"number"Input schema / properties / column_id / $refPrevious value: -"#/properties/bucket_id"New value: +"#/properties/card_id"Input schema / properties / position / descriptionPrevious value: -"Position within the destination column (zero-indexed). If not specified, card will be added to the end of the column."New value: +"1-indexed position within the destination column (1 = top). If not specified, the card is added to the top of the column."Input schema / properties / position / exclusiveMinimumAdded value: +0Input schema / properties / position / minimumRemoved value: -0Input schema / requiredPrevious value: -[
- "bucket_id",
- "card_id",
- "column_id"
-]New value: +[
+ "card_id",
+ "column_id"
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint false, destructiveHint false, and idempotentHint false. The description adds no additional behavioral context beyond the basic move action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single short sentence that efficiently conveys the core purpose. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the basic purpose but omits information about return values, side effects, or prerequisites. Given the tool's simplicity and absence of output schema, it is minimally adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not elaborate on the parameters beyond what the input schema already provides. The schema covers 67% of parameters with descriptions, but the description field itself adds no parameter-specific meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Move a kanban card to a different column and/or position', which is a specific verb and resource. It distinguishes from sibling tools like create, get, list, and update by focusing on positional changes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like update_kanban_card. The description implies the use case but does not explicitly state exclusions or contexts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/stefanoverna/basecamp-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server