Skip to main content
Glama
chukaibejih

Task Manager MCP Server

by chukaibejih
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_task

Create a new task with a title, description, priority, due date, and tags to capture work items and manage deadlines.

Instructions

Create a new task

Args:
    title: Task title (required)
    description: Detailed description of the task
    priority: Task priority (low, medium, high, urgent)
    due_date: Due date in YYYY-MM-DD format
    tags: Comma-separated tags (e.g., "work,urgent,meeting")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
titleYes
due_dateNo
priorityNomedium
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It says a task is created, but does not disclose side effects, required permissions, persistence behavior, return value, or what happens on invalid input.

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 front-loaded with the action and then structured as an Args list. It is reasonably concise, though the Args block could be tighter and includes some self-evident labels.

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?

The description covers purpose and all parameters, which is adequate for a simple create tool. However, with no annotations and no output schema, it omits behavioral context such as permissions, side effects, and whether the created task or its ID is returned.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate for all five parameters. It documents required title, meaning of description, allowed priority values, due_date format, and tags format, adding meaningful semantics beyond the bare schema.

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 states a specific verb and resource: 'Create a new task.' This clearly distinguishes it from CRUD siblings like update_task, delete_task, and complete_task, but it does not explicitly call out the distinction or alternative tools.

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 gives no guidance on when to use this tool versus alternatives, no prerequisites, and no conditions for choosing create_task over update_task or other siblings. It only states what the tool does.

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