Skip to main content
Glama

task_create

Creates a standalone user task not tied to a process instance, enabling ad-hoc work items with name, assignee, priority, and due date.

Instructions

Create a standalone user task not attached to a process instance. Useful for ad-hoc work items. Provide name, assignee, priority, and due date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "task_create"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
  2. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It conveys that this is a mutating create operation, but says nothing about required permissions, whether the task is immediately claimable/assignable, what happens if the assignee is unknown, or what the call returns (e.g. a new task id) — a notable gap given there is no output schema either.

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?

Three short sentences, front-loaded with the create action and the key scoping qualifier. No filler; the only weakness is that the final sentence implies a parameter contract the schema does not back up.

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?

For a creation tool with no annotations, no output schema, and an empty input schema, the definition should cover required fields, accepted formats, and at least the shape of the result (new task id). It covers only the conceptual purpose, leaving the agent without enough to call it confidently or know what it gets back.

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?

The input schema declares zero properties (an unconstrained object), yet the description names name, assignee, priority, and due date, so it does add field-level meaning the schema lacks. However, the mismatch means the agent cannot tell whether these are required, what formats priority or due date take, or whether other fields are accepted — unconstrained-schema cases need more specificity than this.

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?

States a specific verb and resource ("Create a standalone user task") and immediately scopes it as "not attached to a process instance," which distinguishes it from process-bound task operations among the siblings like task_complete or task_update. It stops short of naming an alternative outright, but the scope qualifier is enough for an agent to disambiguate.

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?

"Useful for ad-hoc work items" implies the when-to-use case (manual, out-of-process work) but gives no explicit exclusions, prerequisites, or alternative to pick instead when a task should be process-attached. Usage is inferable rather than stated.

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

Deploy Server

Other Tools