Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Create a new bug card based on provided card id

create_bug_based_on_card

Create a detailed Targetprocess bug from an existing user story, bug, or feature card, generating a structured report with environment, steps to reproduce, expected, and actual behavior.

Instructions

Create a new bug card based on provided card id that summarizes the problem in concise, descriptive manner answering questions What? Where? When?, and content explaining what happened in detail. NOTE: this tool requires a user story, bug, or feature card as a reference (i.e. card ID). CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF you already have user story, bug, or feature card content, proceed to step 3 skipping step 2; 2) ELSE call "get_user_story_content" tool, "get_bug_content" tool, or fetch the feature to get card content; 3) format the new bug inside html tags with Environment (describes where bug was found, dev, feature, review or uat Environment), Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior and Attachments sections (note: section titles should be wrapped in tags, e.g. Issue Description); 4) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 5) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 6) IF the user specified a release by name (not ID), call "get_current_releases" to find the matching release and use its ID as releaseId; 7) add a comment to the card with created bug Id and its Title

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>",
      "card": "<card>",
      "bugContent": "<bugContent>"
    },
    "name": "create_bug_based_on_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYes
titleYesBug card title that summarizes the problem in concise, descriptive, and actionable manner, enabling a developer to understand the issue without opening the report
originNoWhere the bug was found, defaults to "Manual QA" if no origin was specified
teamIdNoOptional Team ID — if user gave a team name, resolve it via "get_teams" first; defaults to TP_TEAM_ID from config
projectIdNoOptional Project ID — if user gave a project name, resolve it via "get_projects" first; defaults to TP_PROJECT_ID from config
releaseIdNoOptional Release ID to assign this bug to — if user gave a release name, resolve it via "get_current_releases" first
bugContentYesComment content to add, explain what happened in detail. Include expected behaviour and what actually occurred. Be specific and avoid assumptions. Clearly outline the actions needed to trigger the bug. Number each step so anyone can follow them easily

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: it creates a card, writes a structured HTML body with mandated sections and <h3> headings, applies config defaults for team/project, and adds a comment containing the new bug's ID and title — a side effect not visible in the schema. It still omits permissions, failure modes, and what the call returns directly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The numbered workflow is scannable and mostly load-bearing, but the opening NOTE restates the first sentence, the title guidance duplicates the schema description, and the HTML formatting instructions are long prose that could be tightened. The ALL-CAPS "CRITICAL WORKFLOW"/"MUST" framing adds noise rather than clarity.

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 7-parameter tool with a nested card object and no output schema, the description covers the orchestration, required body structure, defaults, and a post-creation side effect. It is close to sufficient; only return-value and error behavior are left unstated.

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 coverage is 86%, so the schema already documents card.id, title, origin, teamId, projectId, and releaseId, including the same name-resolution hints repeated here. The description adds little beyond that, and "origin" is only referenced obliquely through the Environment section requirement rather than tied to the enum.

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 states a specific verb and resource ("create a new bug card based on provided card id") and adds that the referenced card must be a user story, bug, or feature. An agent can tell what it produces, but the description never distinguishes it from the sibling "create_bug" or explains which one to pick, leaving that differentiation to inference.

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?

Usage context is unusually explicit: prerequisites (a reference card ID), a branching rule for when to fetch card content via "get_user_story_content"/"get_bug_content", and conditional name-to-ID resolution via "get_teams", "get_projects", and "get_current_releases". The gap is that it never states when NOT to use this tool versus the plain "create_bug" sibling.

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