Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Adds generated test cases to a test plan linked to a TP card (UserStory, Bug, or Feature).

add_test_cases_to_test_plan

Attach generated test cases to a Targetprocess test plan linked to a UserStory, Bug, or Feature. Provide the test plan ID and case details to create and link them.

Instructions

Adds generated test cases to a test plan linked to a TP card (UserStory, Bug, or Feature).

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": {
      "testPlanId": "<testPlanId>",
      "testCases": "<testCases>"
    },
    "name": "add_test_cases_to_test_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
testCasesYesArray of test cases to create in the test plan
testPlanIdYesTest plan ID to add test cases to (e.g. 145789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing beyond "adds". It does not cover permission/auth needs, whether test cases are appended vs replace existing ones, duplicate handling, batch size limits, or what happens on partial failure.

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 no filler or redundancy. Its brevity is not the problem — the problem is that the space saved was not used for anything informative.

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 mutation tool with no annotations and no output schema, so the description should at minimum state side effects and return behavior. Instead it only restates the title, leaving the agent without the behavioral context needed to invoke a write operation confidently.

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% for both parameters, including nested name/description/steps semantics and the HTML formatting convention, so the schema does the heavy lifting. The description adds no meaning beyond it, which makes the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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 when-to-use guidance, no prerequisites (e.g. that the test plan must already exist), and no mention of alternatives. An agent reading this cannot tell why it would pick this tool over write_test_cases or add_test_case_step_by_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