Skip to main content
Glama
Sign In
Local Task Manager MCP Server

Local Task Manager MCP Server

by akbarshaik2243
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

complete_task

Mark a task as completed to update its status and return the updated task. Resolves the need for finalizing tasks with a single action.

Instructions

Mark a task as completed and return the updated task.

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": {
      "task_id": "<task_id>"
    },
    "name": "complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
completedYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It states the action and return value, but omits details such as idempotency, side effects on related data, permission requirements, or behavior when the task is already completed.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose. It avoids unnecessary words, though some important information is missing, which prevents a perfect score.

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?

Given the low complexity (1 parameter, output schema exists), the description is insufficient. It lacks preconditions, error handling, behavioral details, and clarity on what constitutes completion, leaving the agent with gaps.

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

Parameters1/5

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

The input schema has 1 parameter (task_id) with 0% description coverage. The description adds no additional meaning beyond the parameter name, failing to compensate for the lack of schema descriptions. The agent receives no guidance on the parameter's format or constraints.

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 action (mark as completed) and the resource (task), and returns the updated task. It distinguishes from sibling tools: list_tasks lists tasks and delete_task deletes, while this tool completes a specific task.

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

Usage Guidelines3/5

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

The description implies the tool is used to mark a task as completed, but it does not specify when not to use it or provide alternatives. The context is clear but lacks explicit guidance on preconditions or exclusion cases.

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