QASE MCP Server

create_project

Create new projects in QASE test management platform by defining project code, title, and access settings to organize testing workflows.

Instructions

Create new project

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_project"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes
`title`	Yes
`description`	No
`access`	No
`group`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 18, 2025

TDQS

C2.4/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a safe operation, what permissions are required, if it's idempotent, or what happens on success/failure. For a creation tool with zero annotation coverage, this is a critical gap in transparency.

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 with just three words, front-loading the essential action and resource. There is no wasted language or unnecessary elaboration, making it efficient for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters, creation operation), lack of annotations, and no output schema, the description is severely incomplete. It doesn't cover parameter meanings, behavioral traits, usage context, or expected outcomes, failing to provide the necessary context for effective tool invocation.

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

Parameters1/5

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

The description adds no parameter information beyond what the input schema provides. With 0% schema description coverage and 5 parameters (code, title, description, access, group), the description fails to explain what these parameters mean, their formats, or constraints. This leaves key inputs like 'access' enum values unexplained.

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 'Create new project' clearly states the action (create) and resource (project), making the purpose immediately understandable. It distinguishes from sibling tools like 'list_projects' or 'get_project' by specifying creation rather than retrieval. However, it doesn't specify what kind of project or domain (e.g., software, construction), which prevents a perfect score.

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. It doesn't mention prerequisites (e.g., authentication), when not to use it, or how it differs from similar creation tools like 'create_case' or 'create_suite'. This leaves the agent with minimal context for tool selection.

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