Skip to main content
Glama

finalize_project

Mark a project as complete in the taskqueue-mcp server when all tasks are done and approved, finalizing the workflow in one step.

Instructions

Mark a project as complete. Can only be called when all tasks are both done and approved. This is typically the last step in a project workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe ID of the project to finalize (e.g., proj-1).

Implementation Reference

  • The tool executor that implements the core logic for the 'finalize_project' tool. It validates the projectId argument and calls taskManager.approveProjectCompletion(projectId) to mark the project as complete.
    const finalizeProjectToolExecutor: ToolExecutor = {
      name: "finalize_project",
      async execute(taskManager, args) {
        // 1. Argument Validation
        const projectId = validateProjectId(args.projectId);
    
        // 2. Core Logic Execution
        const resultData = await taskManager.approveProjectCompletion(projectId);
    
        // 3. Return raw success data
        return resultData;
      },
    };
  • Defines the Tool object for 'finalize_project' including its name, description, and inputSchema that requires a 'projectId' string.
    const finalizeProjectTool: Tool = {
      name: "finalize_project",
      description: "Mark a project as complete. Can only be called when all tasks are both done and approved. This is typically the last step in a project workflow.",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "The ID of the project to finalize (e.g., proj-1).",
          },
        },
        required: ["projectId"],
      },
    };
  • Registers the finalizeProjectToolExecutor in the toolExecutorMap used by the executeToolAndHandleErrors function.
    toolExecutorMap.set(finalizeProjectToolExecutor.name, finalizeProjectToolExecutor);
  • Includes the finalizeProjectTool in the exported ALL_TOOLS array for MCP tool registration.
    finalizeProjectTool,
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the precondition ('all tasks are both done and approved') and workflow context, but lacks details on permissions, side effects, or response format. It adequately describes the core behavior but misses some operational aspects.

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 two sentences with zero waste: the first states the action and precondition, the second provides workflow context. It is front-loaded with the core purpose and appropriately sized for the tool's complexity.

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

Completeness4/5

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

Given the tool's moderate complexity (mutation with a precondition), no annotations, and no output schema, the description is mostly complete. It covers purpose, usage, and behavioral context well, but could benefit from mentioning response format or error conditions to be fully comprehensive.

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?

The schema description coverage is 100%, so the schema fully documents the single parameter. The description does not add parameter details beyond the schema, but with only one parameter, the baseline is high. It implies the projectId is used to identify the project to finalize.

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?

The description clearly states the specific action ('Mark a project as complete') and resource ('project'), distinguishing it from siblings like create_project or update_task. It precisely defines the verb and target, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('when all tasks are both done and approved') and positions it in the workflow ('typically the last step in a project workflow'). It provides clear context for usage without needing to reference alternatives directly.

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/chriscarrollsmith/taskqueue-mcp'

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