Skip to main content
Glama
devirokkam

Task MCP Server

by devirokkam
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

complete_task

Mark a task as completed by providing its ID to update task status in the Task MCP Server's management system.

Instructions

Mark a task as completed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesID of the task to complete

Implementation Reference

  • src/task_mcp_server/server.py:123-140 (handler)
    The handler logic for "complete_task" which updates the in-memory task dictionary to mark a task as completed.
    elif name == "complete_task":
    task_id = int(arguments.get("task_id", 0))
    
    if task_id not in tasks:
        return [
            types.TextContent(
                type="text",
                text=f"❌ Task {task_id} not found"
            )
        ]
    
    tasks[task_id]["completed"] = True
    return [
        types.TextContent(
            type="text",
            text=f"✅ Task {task_id} marked as completed: {tasks[task_id]['title']}"
        )
    ]
  • src/task_mcp_server/server.py:44-57 (schema)
    The schema definition for "complete_task" within the list_tools method.
    types.Tool(
    name="complete_task",
    description="Mark a task as completed",
    inputSchema={
        "type": "object",
        "properties": {
            "task_id": {
                "type": "number",
                "description": "ID of the task to complete"
            }
        },
        "required": ["task_id"]
    }
),

Tool Definition Quality

C2.9/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 disclosure burden. It implies a mutation (marking complete) but fails to specify idempotency, error conditions (e.g., invalid task_id), side effects, or whether the operation is reversible (can it be un-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?

Extremely brief at four words with zero redundancy. While appropriately sized for a single-parameter tool, the extreme brevity contributes to the lack of behavioral and contextual detail found in other dimensions.

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?

Adequate for a simple CRUD operation with full schema coverage and no output schema, but minimal given the absence of annotations. Lacks disclosure of error behaviors, return values, or side effects that would help an agent handle edge cases.

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%, establishing a baseline of 3. The description 'Mark a task as completed' implies the 'task_id' parameter refers to an existing task, but adds no syntax guidance, format constraints, or semantic context beyond what the schema already provides.

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?

States a specific verb ('Mark') and resource ('task') with clear state change ('as completed'). However, it does not explicitly differentiate from sibling tools (e.g., distinguishing an update operation from 'delete_task' or confirming behavior differs from 'add_task').

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?

Provides no guidance on when to use this tool versus alternatives, prerequisites for invocation (e.g., task must exist), or what happens if the task is already completed. Contains no 'when-not' or alternative recommendations.

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/devirokkam/MCP_Github_Deployment'

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