Skip to main content
Glama
stefanoverna

Basecamp MCP Server

by stefanoverna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Move Basecamp Todo

basecamp_move_todo
Idempotent

Move an incomplete Basecamp todo within its list, into a group, or to another todo list. Set order with top, bottom, before, or after placement.

Instructions

Move a todo to a different place: in its todo list, into a group (section), or into a different todo list.

Examples:

  • Put a todo at the top of its list: placement "top".

  • Put a todo after another todo: placement "after" and relative_to_id. If the other todo is in a different list or group, the todo moves there.

  • Move a todo to the bottom of another list or group: placement "bottom" and destination_id.

Only the todos that are not complete have a position. To set the order of many todos, use basecamp_reorder_todos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
todo_idYesBasecamp resource identifier
placementYesWhere to put the item. 'before' and 'after' need relative_to_id.
destination_idNoID of the todo list or group to move the todo into. If you do not give it, the todo goes into the parent of relative_to_id, or else it stays in its current parent.
relative_to_idNoID of the item to put this item before or after. Use it only with placement 'before' or 'after'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, open-world behavior, lower the bar. The description adds genuinely useful semantics: 'If the other todo is in a different list or group, the todo moves there,' and 'Only the todos that are not complete have a position,' which the annotations do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded one-line summary followed by tightly scoped examples; each sentence earns its place. Slightly verbose example block, but no filler.

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

Completeness5/5

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

No output schema exists, but the description, annotations, and 100%-covered schema together give an agent everything needed to select and invoke the tool correctly, including cross-list behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining the interaction between destination_id and relative_to_id (fallback to the parent of relative_to_id, or staying in place), adding real meaning.

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

Purpose5/5

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

States a specific verb and resource (move a todo) and enumerates the three distinct destinations: within its list, into a group/section, or into another list. It clearly separates itself from the sibling basecamp_reorder_todos by naming it.

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 three worked examples effectively show when each placement mode applies, and it explicitly routes bulk ordering to basecamp_reorder_todos. It lacks an explicit statement of when NOT to use this tool (e.g., cross-project limits), but the context is clear.

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