Skip to main content
Glama
Sign In
testit-mcp-server

testit-mcp-server

by iampopovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_test_plan_clone

Clone an existing TestIT test plan by UUID to create a copy with a “(1)” name suffix and New status; returns the new plan.

Instructions

Clone a test plan (copy named " (1)", status New). Returns the new plan.

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": {
      "id": "<id>"
    },
    "name": "create_test_plan_clone"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSource test plan UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description only needs to add operational detail — and it does, disclosing the auto-generated name suffix, the initial status of the copy, and that the new plan is returned. What is missing is the depth of the copy: whether suites, test points, configurations, or history come along, which is the main behavioral question for a clone.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action, with the naming/status behavior immediately after and the return value last. Nothing is redundant or padded.

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 one-parameter mutation tool with no output schema, the definition covers action, resulting name, resulting status, and return form. The remaining gap — scope of what gets cloned and whether the copy is fully independent — is real but modest given the tool's simplicity.

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?

There is a single parameter with 100% schema description coverage ("Source test plan UUID"), so the schema does the work and the baseline of 3 applies. The description implies the id is the source being copied but adds no format or failure semantics beyond the schema.

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?

Uses a specific verb plus resource ("Clone a test plan") and adds distinguishing detail the sibling create_test_plan would not have: the copy is named "<name> (1)" and starts in status New. That is enough to tell the two apart in practice, though it never explicitly contrasts itself with create_test_plan.

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?

Use is only implied by the verb 'clone' — an agent can infer it is for duplicating an existing plan rather than authoring a new one. There is no statement of when to prefer this over create_test_plan, nor any prerequisite such as needing read access on the source plan.

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