Skip to main content
Glama

add_task

Create new tasks with titles and optional descriptions for personal task management within Claude Desktop.

Instructions

Add a new task to the task list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title
descriptionNoTask description (optional)

Implementation Reference

  • The logic that executes when the add_task tool is called.
    if name == "add_task":
        task_counter += 1
        title = arguments.get("title", "")
        description = arguments.get("description", "")
        
        tasks[task_counter] = {
            "id": task_counter,
            "title": title,
            "description": description,
            "completed": False
        }
        
        return [
            types.TextContent(
                type="text",
                text=f"✅ Task added successfully!\nID: {task_counter}\nTitle: {title}"
            )
        ]
  • Schema definition for the add_task tool.
    types.Tool(
        name="add_task",
        description="Add a new task to the task list",
        inputSchema={
            "type": "object",
            "properties": {
                "title": {
                    "type": "string",
                    "description": "Task title"
                },
                "description": {
                    "type": "string",
                    "description": "Task description (optional)"
                }
            },
            "required": ["title"]
        }
    ),
Behavior2/5

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

No annotations provided, so description must carry full behavioral burden. It fails to disclose: return value (e.g., task ID), idempotency behavior, duplicate handling, or side effects. 'Add' implies mutation but lacks critical execution context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no redundancy, appropriately brief. However, brevity crosses into under-specification given lack of annotations and mutation behavior that requires disclosure.

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?

Insufficient for a mutation tool with zero annotations and no output schema. Missing behavioral contract, sibling differentiation, and execution prerequisites that an agent needs to select and invoke correctly.

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 has 100% description coverage ('Task title', 'Task description'), meeting baseline expectations. Description text adds no parameter semantics beyond schema, but none are needed given complete schema documentation.

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?

Clear verb ('Add') + resource ('task') + scope ('to the task list'). States what the tool does without ambiguity. However, it does not explicitly distinguish from sibling 'complete_task' or clarify that this creates vs. modifies existing tasks.

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 siblings like 'complete_task' or 'delete_task'. No prerequisites, constraints, or conditions mentioned.

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