QASE MCP Server

get_cases

Retrieve test cases from a Qase project using filters like search terms, milestone, suite, severity, priority, type, behavior, automation status, and external issue tracking.

Instructions

Get all test cases in a 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>"
    },
    "name": "get_cases"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes
`search`	No
`milestoneId`	No
`suiteId`	No
`severity`	No
`priority`	No
`type`	No
`behavior`	No
`automation`	No
`status`	No
`externalIssuesType`	No
`externalIssuesIds`	No
`include`	No
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 18, 2025

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation ('Get') but doesn't disclose critical traits like pagination behavior (hinted by 'limit' and 'offset' parameters), rate limits, authentication needs, or whether results are sorted. This leaves significant gaps for agent decision-making.

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 a single, clear sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 complexity (15 parameters, no output schema, no annotations), the description is severely incomplete. It doesn't address parameter usage, return values, error conditions, or behavioral constraints, leaving the agent with insufficient context to use the tool effectively beyond basic intent.

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%, so the description must compensate but fails to do so. It mentions 'all test cases in a project' but doesn't explain any of the 15 parameters, including the required 'code' parameter or filtering options like 'search' or 'severity'. This leaves parameters largely undocumented.

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 clearly states the action ('Get') and resource ('test cases in a project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_case' (singular) or explain the scope of 'all' versus filtered results, 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 like 'get_case' (singular) or 'get_suites' (for related resources). It lacks context about prerequisites, such as needing a project code, or when filtering might be preferred over retrieving all cases.

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