Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Create a new task

create_task

Create a task and link it to a specific user story by providing a title and user story ID, with an optional description for context.

Instructions

Create a new task linked to a user story.

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

Input Schema

NameRequiredDescriptionDefault
titleYesTask title
descriptionNoTask description (optional)
userStoryIdYesUser story ID to link the task to (e.g. 145789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only says a task is created and linked. It does not state permission requirements, whether a task ID is returned, whether state/status defaults are applied, or whether the userStoryId must already exist.

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 front-loaded sentence with zero padding, stating action and linkage immediately. It is efficient, though arguably terse enough that a second sentence of behavioral context would have been worth the space.

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

Completeness3/5

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

For a simple three-parameter creation tool with full schema coverage and no output schema, the description covers the essential action. It leaves gaps around the return value and side effects (default fields, required story existence) that an agent would want before invoking it.

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%, so all three parameters (title, description, userStoryId) are already documented in the schema with an example ID format. The description adds only the linking relationship, which is already implied by userStoryId's own schema text, so it neither compensates nor detracts.

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 gives a specific verb and resource ("Create a new task") plus the key relationship ("linked to a user story"), which lets an agent distinguish it from create_user_story or create_bug. It stops short of explicitly contrasting with any named sibling, so it is clear but not fully differentiated.

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 guidance on when to create a task versus a user story, bug, or epic, and no prerequisites or exclusions are stated. The only usage signal is the implicit dependency on an existing user story ID.

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