Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Write test cases for a TP card (UserStory, Bug, or Feature)

write_test_cases

Fetches a Targetprocess card by ID, analyzes its details, and generates structured test cases covering happy paths, edge cases, boundaries, and errors for test plan creation.

Instructions

Fetches a TP card (UserStory, Bug, or Feature) content by ID. CRITICAL WORKFLOW — after receiving the card content, you MUST: 1) Thoroughly analyze the card name and description to understand the feature or issue being tested 2) Write detailed test cases covering: happy path, edge cases, boundary conditions, and error scenarios 3) For each test case produce: - name: concise action-oriented title - description: HTML with Preconditions and Test Type sections only (no steps here) - steps: ordered array of { description: "", result: "" } 4) Call "create_test_plan" tool passing: resourceId (the card id), resourceType, testPlanTitle (use the card name/title), NOTE: IF test plan already exists - skip this step and proceed to step 5. 5) Call "add_test_cases_to_test_plan" tool passing: testPlanId (the test plan id), and the testCases array with name, description, and steps

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

Input Schema

NameRequiredDescriptionDefault
resourceIdYesTP card ID (e.g. 145789)
resourceTypeNoType of the TP 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
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that the tool reads card content while the writes happen in downstream tools. However, it never states whether this tool itself persists anything, what the returned card content includes, or any permission/side-effect profile for a name that implies mutation.

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 well-structured and front-loads the fetch behavior, but the bulk of the text is instructions for the two downstream tools rather than for this one, which is scope creep for a 2-parameter call. The nested bullet spec for test case shape is useful but heavy.

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?

The description covers the intended workflow end-to-end, which is substantial for a no-annotation, no-output-schema tool. It still omits what the fetch actually returns (field names/shape) and whether the call has side effects, leaving the agent without full information to call it safely.

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 100%, so both parameters are already documented. The description only restates that resourceId is the card id and that it should be forwarded to create_test_plan with resourceType, adding no format, constraint, or defaulting insight beyond the schema's enum and default.

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

Purpose3/5

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

The title and name promise that the tool writes test cases, but the first sentence says it only "Fetches a TP card ... content by ID," leaving the tool's actual effect ambiguous. It does name the sibling tools it hands off to (create_test_plan, add_test_cases_to_test_plan), which aids differentiation, but the core verb/resource mismatch forces the agent to guess whether calling this tool creates anything.

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?

The CRITICAL WORKFLOW section gives explicit sequencing and even a branch condition: if a test plan already exists, skip create_test_plan and go to step 5. It lacks guidance on when to prefer the read-only siblings (e.g. get_user_story_test_cases) over this workflow, so it stops short of full when-not coverage.

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