Skip to main content
Glama

Create task

create_task

Create a task under a project. Tasks group the subtasks that time is logged against. The task inherits its allowed billing types from the parent project. Discover ids with find_billing_work - never ask the user for an 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": {
      "project_id": "<project_id>",
      "name": "<name>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTask name (required).
project_idYesId of the parent project (required). Must be a project in your organization.
descriptionNoOptional task description.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
create_general_activityNoOptional. When true (the default for this tool), also create a default visible "General" activity under the task so time can be logged immediately. Set false to create a task with no activities yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds useful domain behavior about billing-type inheritance from the parent project, but it does not cover permissions, side effects beyond that, or what is returned.

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?

The description is four focused sentences, front-loads the core action, and each sentence adds either domain context or an actionable instruction. There is no redundant or filler wording.

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

Completeness4/5

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

For a create mutation with full schema coverage, the description covers purpose, hierarchy, billing inheritance, and ID discovery adequately. It could be slightly more complete by mentioning the return value or key side effects, but the supplied annotations and schema fill most remaining gaps.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are already well documented. The description adds meaningful procedural guidance for project_id by directing callers to discover IDs with find_billing_work and never ask the user for an ID, though it does not add much for the remaining parameters.

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 clearly states 'Create a task under a project,' naming a specific verb and resource, and clarifies that tasks group subtasks. It does not explicitly contrast itself with creation siblings such as create_subtask or create_project, so sibling differentiation is only implicit.

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

Usage Guidelines3/5

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

Usage is implied by 'Create a task under a project,' and it gives a practical instruction to use find_billing_work for IDs. It does not state when to use this tool versus update_task, move_task, create_subtask, or other alternatives, nor does it provide exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources