Skip to main content
Glama

complete_task

Mark a task as completed by providing its UUID, enhancing task management within the MCP Think Tank system for efficient problem-solving workflows.

Instructions

Mark a task as completed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUUID of the task to mark as completed

Implementation Reference

  • The complete_task tool registration and handler implementation. Validates the task ID using CompleteTaskSchema, retrieves the task from storage, updates its status to 'done', and returns the result as JSON.
    server.addTool({
      name: "complete_task",
      description: "Mark a task as completed.",
      execute: async (params: any) => {
        try {
          // Validate input parameters
          const validatedParams = CompleteTaskSchema.parse(params);
          const task = taskStorage.get(validatedParams.id);
          
          if (!task) {
            return JSON.stringify({
              error: `Task with ID ${validatedParams.id} not found`
            });
          }
          
          // Update task status to done
          const updatedTask = taskStorage.update(validatedParams.id, { 
            status: "done"
          });
          
          return JSON.stringify({
            task: updatedTask,
            message: "Task marked as completed"
          });
        } catch (error) {
          return JSON.stringify({ 
            error: `Invalid complete_task parameters: ${error instanceof Error ? error.message : String(error)}`
          });
        }
      }
    });
  • Zod schema defining the input parameters for the complete_task tool: a required UUID string for the task ID.
    // Schema for complete_task parameters
    const CompleteTaskSchema = z.object({
      id: z.string().uuid()
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Mark as completed' implies a mutation operation, but it doesn't specify whether this is reversible, what permissions are required, how it affects task status, or what happens if the task is already completed. This leaves critical behavioral aspects undocumented.

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 extremely concise with a single sentence that directly states the tool's purpose. There's no wasted words or unnecessary elaboration, making it front-loaded and efficient for quick understanding.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what 'completed' means in this context, what the tool returns (e.g., success confirmation, updated task object), or error conditions. Given the complexity of task management and rich sibling toolset, more context is needed.

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 description doesn't mention any parameters, but schema description coverage is 100% with a single well-documented 'id' parameter (UUID of the task). This meets the baseline of 3 since the schema adequately covers parameter semantics, though the description adds no value beyond what's already in the structured data.

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 ('Mark as completed') and resource ('task'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'update_tasks' or 'list_tasks' which might also handle task completion, leaving some ambiguity about why this specific tool exists.

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 like 'update_tasks' or 'list_tasks'. There's no mention of prerequisites (e.g., task must exist, be in progress), exclusions, or typical scenarios for completion versus other task operations.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/flight505/mcp-think-tank'

If you have feedback or need assistance with the MCP directory API, please join our Discord server