Skip to main content
Glama

Create Task

create_task

Create a new project task with title, phase, priority, dependencies, and acceptance criteria to organize and sequence work.

Instructions

Create a new task with phase, priority, dependencies, and description.

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": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
phaseNoWhich phase this task belongs to (leave empty for current phase).
titleYesShort task title.
priorityNoOne of: critical, high, medium, low.medium
depends_onNoComma-separated task IDs that must be completed first.
descriptionNoLonger description / acceptance criteria.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about side effects, persistence (does it write to the project brain/workspace?), prerequisites such as an initialized project, or whether dependencies are validated. For a mutation tool with zero annotation coverage this is a meaningful gap.

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?

A single tight sentence with no filler, and the resource and key attributes are front-loaded. It is efficient but so short that it omits the routing information an agent needs.

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?

An output schema exists and the input schema is fully documented, so return-value explanation is unnecessary. But with no annotations and an obvious overlapping sibling (`add_task`), the description should explain persistence and disambiguation; as written, an agent lacks what it needs to choose and call this confidently.

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% and each parameter is well documented in the schema itself (including the priority value list and the comma-separated depends_on format). The description merely echoes the parameter names (phase, priority, dependencies, description) without adding format or edge-case meaning, so the baseline of 3 applies.

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 names a specific verb and resource ("Create a new task") and enumerates the main attributes (phase, priority, dependencies, description), so the operation is immediately understandable. However, it does nothing to distinguish this tool from the sibling `add_task`, which appears to perform an overlapping function, so an agent still cannot tell them apart on purpose alone.

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 at all: no statement about when to prefer create_task over add_task, or how it relates to update_task/complete_task. The only implied context is 'creating a task', which the name already conveys.

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