QASE MCP Server

create_suite

Create a new test suite in QASE test management platform to organize test cases by defining code, title, description, and parent relationships.

Instructions

Create a new test suite

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": {
      "code": "<code>",
      "title": "<title>"
    },
    "name": "create_suite"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes
`title`	Yes
`description`	No
`preconditions`	No
`parent_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 18, 2025

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Create a new test suite' implies a write/mutation operation, but there's no information about permissions required, whether creation is idempotent, what happens on failure, or what the response contains. For a creation tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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?

The description is extremely concise - just 4 words. It's front-loaded with the essential action and resource. There's zero wasted language or redundancy. While it may be too brief for completeness, as a standalone statement it's perfectly structured and efficient.

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?

For a creation tool with 5 parameters, 0% schema description coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what a test suite is in this context, what parameters mean, what the creation entails, or what to expect as a result. The agent would struggle to use this tool correctly without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the 5 parameters have descriptions in the schema. The tool description provides no information about parameters whatsoever - not what 'code', 'title', 'description', 'preconditions', or 'parent_id' mean or how they should be used. The description fails to compensate for the complete lack of schema documentation.

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 description 'Create a new test suite' clearly states the verb ('create') and resource ('test suite'), which is better than a tautology. However, it doesn't differentiate from siblings like 'create_project' or 'create_plan' - all could be creating different types of test artifacts. The purpose is clear but lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'create_project', 'create_plan', and 'create_case', there's no indication of when a test suite is appropriate versus other test artifacts. No prerequisites, constraints, or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.