Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Create a new test plan linked to a TP card

create_test_plan

Create a new test plan linked to a UserStory, Bug, or Feature by providing a title and card ID. Add an optional description or specify the resource type.

Instructions

Create a new test plan linked to a UserStory, Bug, or Feature. Name and Project are required by the API; Description, StartDate, and EndDate are optional.

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>",
      "resourceId": "<resourceId>"
    },
    "name": "create_test_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTest plan title — use the linked card name
resourceIdYesID of the card to link this test plan to (e.g. 145789)
descriptionNoOptional description of the test plan scope or goals
resourceTypeNoType of the linked card — UserStory, Bug, or Feature (default: UserStory)UserStory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: no permissions, no failure modes, no indication of what is returned on success. Worse, it claims 'Name and Project are required by the API' while the schema requires title and resourceId and contains no Project field at all, which can send an agent looking for a nonexistent parameter.

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?

Two tight sentences, front-loaded with the action and resource, with no filler. The second sentence's required/optional summary is compact and useful in principle, though it introduces the erroneous 'Project' reference that a sharper version would have avoided.

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 four-parameter creation tool with a fully documented schema and no output schema, most of what an agent needs is present. However, with zero annotations and no return-value description, the definition leaves open what a successful call yields (presumably a new plan ID) and what happens to the linked card.

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 the schema already explains all four parameters, including the enum and default for resourceType — baseline 3 applies. The description adds no format or constraint detail beyond restating required versus optional, and its 'Project' reference conflicts with the actual parameter set.

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 opens with a specific verb plus resource — 'Create a new test plan' — and states the link target (UserStory, Bug, or Feature). This cleanly separates it from read-oriented siblings like get_test_plan_by_id and from follow-up tools like add_test_cases_to_test_plan, though it never names an alternative explicitly.

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?

Usage is only implied: it is clearly the creation entry point for a plan attached to an existing card. There is no statement of prerequisites (must the card already exist?), no when-not-to-use, and no pointer to add_test_cases_to_test_plan as the natural next step.

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