Skip to main content
Glama
qase-tms

Qase MCP Server

Official
by qase-tms

create_case

Create a new test case in a Qase project by specifying title, description, steps, preconditions, and other test attributes.

Instructions

Create a new test case in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesProject code (2-10 uppercase letters, numbers, or underscores)
titleYesTest case title
descriptionNoTest case description
preconditionsNoPreconditions for the test
postconditionsNoPostconditions after the test
severityNoTest severity (label or numeric ID from the current workspace configuration)
priorityNoTest priority (label or numeric ID: 0=not set, 1=high, 2=medium, 3=low)
typeNoTest type (label or numeric ID: 1=functional, 2=smoke, 3=regression, 4=security, 5=usability, 6=performance, 7=acceptance)
layerNoTest layer (label or numeric ID from workspace configuration)
is_flakyNoMark test case as flaky
suite_idNoSuite ID to organize test case
milestone_idNoMilestone ID
behaviorNoTest behavior (label or numeric ID from workspace configuration)
automationNoAutomation status
statusNoTest case status (label or numeric ID from workspace configuration)
stepsNoArray of test steps
steps_typeNoStep format: 'classic' for structured steps, 'gherkin' for Given/When/Then scenarios
tagsNoTags for categorization
attachmentsNoArray of attachment hashes
custom_fieldNoCustom field values
Behavior3/5

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

Annotations already indicate non-read-only and non-destructive behavior. The description does not add any additional behavioral context (e.g., permissions, side effects, reversibility), so it only meets the baseline with annotations present.

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?

Extremely concise: a single sentence that conveys the purpose without any fluff. Every word is necessary.

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?

Given the high complexity (20 parameters, nested objects) and lack of output schema, the description is too sparse. It does not explain required parameters, behavior with nested structures, or return values, making it incomplete for an agent.

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% with detailed descriptions for all parameters. The description adds no extra parameter meaning beyond the schema, so it scores at the baseline of 3.

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

Purpose5/5

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

The description clearly states the action ('Create'), the resource ('test case'), and the context ('in a project'). It effectively distinguishes from sibling tools like 'bulk_create_cases' and 'update_case'.

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?

No explicit guidance on when to use this tool versus alternatives like 'bulk_create_cases' or 'update_case'. The description is neutral but lacks explicit usage scenarios or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/qase-tms/qase-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server