Skip to main content
Glama

ui_create_task

Create a task or sub-task from the UI within a project, with optional parent, brief, files, and target tests for structured work planning.

Instructions

App-only: create a task or sub-task from the UI.

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

Input Schema

NameRequiredDescriptionDefault
briefNo
filesNo
titleYes
parent_idNo
project_idYes
target_testsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It says this creates a task or sub-task, but it does not disclose permissions, side effects, duplicate handling, parent-child constraints, or what happens with files and target tests.

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 a single short sentence with the key scope qualifier front-loaded. Every part earns its place, with no wasted wording.

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?

This is a six-parameter mutation tool with no annotations, no output schema, and no schema descriptions. The description states the basic purpose but is far too thin to make the tool fully understandable for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate by explaining the six parameters. It only hints at sub-task creation via parent_id and does not clarify project_id, title, brief, files, or target_tests meaningfully.

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?

It states a specific verb and resource: create a task or sub-task. The 'App-only' and 'from the UI' qualifiers give useful scope, though the description does not explicitly differentiate this from sibling tools such as task_plan or ui_update_task.

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?

'App-only' implies this is intended for UI-based creation rather than programmatic or planning workflows. However, there is no explicit guidance on when to use this versus alternatives, no prerequisites, and no exclusions.

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