Skip to main content
Glama

Create Task

create_task

Create a task — an owned unit of work with a status, priority, and optional assignee. Use assignee: "agent" to assign it to yourself as the calling agent; omit to leave unassigned. Pass project_key to file it under an adopted Project, or project_id (from list_projects) for a Project with no key, not both. Pass parent_task_id to create it as a subtask of a task you own — a subtask is a full task, and nesting is bounded to one level (a subtask cannot itself have subtasks). Pass due_at (ISO 8601) for an optional due date/time — display-only, no reminders are sent. In your own Gryz, pass note with status: "blocked" or "human_review" to say what you need from a person. Subject to the plan's open-task quota.

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
bodyNoOptional Markdown body
noteNoIn your own Gryz: what you need from a person, when you create this as blocked or human_review. The person sees it on their Tasks page. Up to 300 characters.
titleYesTask title, 1–200 characters
due_atNoOptional ISO 8601 due date/time. Display-only, no reminders.
statusNoDefault: open
assigneeNo"me" claims for the calling user (session only); "agent" assigns to the calling team member or connection (token only); or a team member handle to assign to that team member. Omit to leave unassigned.
priorityNoDefault: normal
project_idNoProject id from list_projects. In your own Gryz, use it for a Project with no project_key, and pass project_key or project_id, not both. In a company it is required.
project_keyNoAdopted Project key to file this task under
parent_task_idNoCreate as a subtask of a task you own. Nesting is bounded to one level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations (which only state it is a non-idempotent, non-destructive write): a plan open-task quota, one-level nesting limit, display-only due dates with no reminders, and visibility of the note to a person. These are exactly the operational constraints an agent needs before calling a mutation tool.

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?

Front-loaded with the definition, then parameter guidance in a compact sequence with no filler sentences. It is dense for one paragraph but every clause carries a distinct constraint; slight tightening around the project_key/project_id rules would help readability.

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?

Covers the tricky parts of a 10-parameter mutation tool (assignment, project filing, nesting, quota) despite having no output schema. It leaves title, body, and priority entirely to the schema and never says what the call returns, which keeps it just short of complete.

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 the baseline is 3; the description earns above that by explaining cross-parameter semantics the schema states only in fragments — project_key/project_id mutual exclusion, the required-in-company case, subtask nesting bound, and the intent behind the 'agent' assignee value.

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?

States a specific verb and resource and goes further to define what a task is ('an owned unit of work with a status, priority, and optional assignee'), which separates it from sibling creators like create_note or create_poll.

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

Usage Guidelines4/5

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

Gives concrete situational rules: use assignee 'agent' to claim for yourself, omit to leave unassigned, pass project_key or project_id but not both, use parent_task_id only for subtasks of tasks you own, and use note when creating blocked/human_review tasks. It never states when to create a task versus other tools (e.g., update_task for existing work), so it stops short of full alternative routing.

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.