Skip to main content
Glama

Add Task Tool

add_task

Create a single project task for yourself, a colleague, or anyone to take, with optional notes, due date, or repeat schedule.

Instructions

Creates one task on a project: free (anyone can take it), for the person themself ("me") or for a colleague who works on the project, with optional notes (steps as - [ ] lines), a due date or a repeat. Use it only when the person asks, after confirming the title and who does it; for an idea for later pass it as an idea, to change an existing task use update_task, to start working on one use start_task. Fails on archived projects or when the assignee is not on the project. Returns the task, with its number (#id).

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

Input Schema

NameRequiredDescriptionDefault
dueNoOptional due date, YYYY-MM-DD, when the person gives one ("by Thursday").
ideaNotrue: an idea for later (the person says "idea", "someday", "note this"), not work to do now; it has no person and stays out of the open tasks.
repoNoThe git remote of the working directory (git remote get-url origin). Preferred: it finds the project by itself.
notesNoOptional details, in Markdown (a list, - [ ] steps, `code`, links).
titleYesShort and concrete, e.g. "Newsletter sign-up form".
repeatNoOptional, when the person says it comes back ("every month", "every Monday"): when it is done, the next one is added by itself, due one interval later. Give a due date too (the first one).
projectNoProject slug or name, when there is no repo.
sessionNoThis session's id, from the cemainou line at the start of the session. The session's project wins over the repo.
assigneeNo"me", a colleague's name or email; leave empty for a free task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

This description is remarkably transparent regarding failure and success. It lists specific preconditions for failure ('Fails on archived projects or when the assignee is not on the project') and clearly defines the output ('Returns the task, with its number (#id)'). Without annotations, the description handles the full burden of disclosure.

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

Conciseness5/5

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

Despite the high density of information (usage guidelines, failure modes, return values), the text is efficiently structured. It packs maximum utility into a concise paragraph without repetitive phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 9 parameters and the need to cover several logical paths (idea vs. work, self vs. colleague, repetition, failure states), the description is highly complete. No critical operational step or constraint is missing.

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?

While schema coverage is 100%, the description adds semantic depth that the schema lacks. For example, it clarifies that notes should include steps as '- [ ] lines' and defines the logic for the 'idea' flag, which is not intuitive from the boolean name alone.

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 purpose is immediately clear: it 'Creates one task on a project.' It specifically scopes the creation, defining who the task is for ('me' or a colleague) and the nature of the content (notes, due date, repeat).

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

Usage Guidelines5/5

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

It provides extremely prescriptive usage rules, stating it should 'Use it only when the person asks.' Crucially, it explicitly routes the user to alternatives: `update_task` for changes and `start_task` for working on existing tasks.

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