Basecamp MCP Server

Complete Basecamp Todo

basecamp_complete_todo

Idempotent

Mark a todo as completed using its Basecamp ID.

Instructions

Mark a todo as completed.

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

Input Schema

Name	Required	Description	Default
`todo_id`	Yes	Basecamp resource identifier

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.2.1Jun 19, 2026

removedInput schema / properties / bucket_id

Removed value: -{
-  "description": "Basecamp resource identifier",
-  "type": "number"
-}

removedInput schema / properties / todo_id / $ref
```
Removed value: -"#/properties/bucket_id"
```
addedInput schema / properties / todo_id / description
```
Added value: +"Basecamp resource identifier"
```
addedInput schema / properties / todo_id / type
```
Added value: +"number"
```

changedInput schema / required

Previous value: -[
-  "bucket_id",
-  "todo_id"
-]New value: +[
+  "todo_id"
+]

Changed2 schema fields changedv1.0.0Jan 4, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedOct 25, 2025

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already indicate idempotentHint=true and readOnlyHint=false, which align with marking a todo complete. The description adds no extra behavioral details (e.g., side effects, permissions), but does not contradict annotations.

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 5-word sentence with zero waste, perfectly concise for a simple action.

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

Completeness3/5

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

For a simple state-change tool with one parameter and good annotations, the description is minimally adequate. However, it lacks context about permissions, return value, or what 'completed' entails, making it slightly incomplete.

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?

The input schema has 100% documentation coverage for its single parameter 'todo_id' as 'Basecamp resource identifier'. The tool description does not enhance this meaning, but baseline is 3.

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 'Mark a todo as completed' clearly states the action and resource, and distinguishes from the sibling tool 'basecamp_uncomplete_todo'. It is direct but could be more explicit about the state change.

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 like 'basecamp_update_todo' (which could also change completion status). There is no mention of prerequisites or contexts where this tool is appropriate or not.

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

Deploy Server