Skip to main content
Glama
langadventurellc

Task Trellis MCP

complete_task

Mark tasks as finished in Task Trellis MCP by recording completion details, updating status to 'done', tracking file changes, and triggering dependent tasks.

Instructions

Completes a task in the task trellis system

Use this tool to mark a task as finished and record completion details. Critical for task lifecycle management and maintaining accurate project status.

Required completion data:

  • 'taskId': Unique identifier of the task being completed

  • 'summary': Concise description of what was accomplished

  • 'filesChanged': Map of modified files with descriptions of changes made

Completion process:

  1. Validates task is in a completable state ('in-progress')

  2. Updates task status to 'done'

  3. Records completion timestamp and summary

  4. Associates file changes with the task for traceability

  5. Updates parent-child relationships and dependency chains

  6. Triggers any dependent tasks that were waiting for this completion

File change tracking:

  • Key: relative file path from project root

  • Value: description of changes made to that file

  • Example: {'src/api/users.ts': 'Added user authentication endpoints', 'tests/auth.test.ts': 'Added comprehensive auth test coverage'}

Best practices:

  • Provide clear, actionable summaries that explain the outcome

  • Document all meaningful file changes for future reference

  • Complete tasks only when all acceptance criteria are met

  • Verify dependent tasks can now proceed before completion

  • Include any important notes or lessons learned in the summary

Task completion automatically notifies dependent tasks and may trigger workflow progression for related work items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesID of the task to complete
summaryYesSummary of the completed task
filesChangedYesMap of files changed with their descriptions
Behavior4/5

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

With no annotations, the description carries full burden and provides rich behavioral details: it describes the multi-step completion process (validation, status updates, timestamp recording, dependency handling), file change tracking specifics, and automatic notifications/triggers. It doesn't mention rate limits or auth needs, but covers most operational behavior thoroughly.

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?

The description is well-structured with clear sections (Required completion data, Completion process, File change tracking, Best practices) and front-loaded purpose. It's appropriately detailed for a complex tool but could be slightly more concise by integrating some best practices into the main flow.

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?

For a mutation tool with no annotations and no output schema, the description provides comprehensive context: it explains the completion process, behavioral effects, parameter usage, and best practices. The only minor gap is lack of explicit error handling or return value information, but overall it's highly complete for the tool's complexity.

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?

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds some context: it explains that 'filesChanged' is a 'Map of modified files with descriptions' and provides an example, but doesn't add significant meaning beyond what the schema provides. Baseline 3 is appropriate given high schema coverage.

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 tool's purpose: 'Completes a task in the task trellis system' and 'mark a task as finished and record completion details.' It distinguishes from siblings like 'claim_task' (which likely starts a task) and 'update_issue' (which modifies but doesn't complete), providing specific verb+resource differentiation.

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?

Explicit guidance is provided: 'Use this tool to mark a task as finished' and 'Critical for task lifecycle management.' It includes when-not scenarios: 'Complete tasks only when all acceptance criteria are met' and 'Verify dependent tasks can now proceed before completion.' This clearly defines usage context versus alternatives.

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

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/langadventurellc/task-trellis-mcp'

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