Skip to main content
Glama

Add Task

add_task

Create and register an active task in the project context so AI assistants can track required work, status, notes, and branch details across sessions.

Instructions

Add an active task to the project context.

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>",
      "description": "<description>"
    },
    "name": "add_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
notesNoOptional notes.
branchNoOptional git branch name.
statusNoOne of: pending, in_progress, blocked, completed.pending
task_idYesUnique identifier (e.g. 'TASK-1', 'feat-auth').
descriptionYesWhat needs to be done.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does little. It implies a mutation of project context state but says nothing about whether tasks persist across sessions, how duplicate task_ids are handled (the schema calls it a unique identifier), whether the status field overrides "active", or what the tool returns.

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?

A single short sentence with no wasted clauses, so it is concise and front-loaded. The problem is under-specification rather than verbosity; the brevity buys no clarity about scope or behavior.

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?

Output schema exists, so return values need not be explained, but for a six-parameter mutation tool with no annotations the definition leaves the key question open: how it differs from create_task. Nothing about persistence, conflict handling, or context effects is addressed.

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 every one of the six parameters is already documented in the schema, including the status value set and the task_id format example. The description adds no meaning beyond that, which is the baseline case for fully covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb and resource ("Add an active task to the project context"), which is more than a tautology, but it does not distinguish this from the sibling create_task, which reads as the same operation. An agent cannot tell from the description alone whether add_task registers an already-existing task with the context tracker or creates a new one.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no mention of create_task, update_task, or add_to_context_list, all of which compete for the same intent. The word "active" hints at status handling but never explains it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.