Skip to main content
Glama
qase-tms

Qase MCP Server

Official
by qase-tms

list_cases

Read-onlyIdempotent

Retrieve test cases from a project, with optional filtering by status, severity, priority, and more. Supports pagination to manage large sets.

Instructions

Get all test cases in a project with optional filtering and pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesProject code (2-10 uppercase letters, numbers, or underscores)
searchNoSearch query for test case title or description
milestone_idNoFilter by milestone ID
suite_idNoFilter by suite ID
severityNoFilter by severity (e.g., "blocker", "critical")
priorityNoFilter by priority (e.g., "high", "medium")
typeNoFilter by type (e.g., "functional", "smoke")
behaviorNoFilter by behavior (e.g., "positive", "negative")
automationNoFilter by automation status
statusNoFilter by status (e.g., "actual", "draft")
external_issues_typeNoFilter by external integration type
external_issues_idsNoFilter by external issue IDs (e.g., Jira ticket keys)
includeNoComma-separated list of entities to include in response (e.g., "external_issues")
limitNoMaximum number of items
offsetNoNumber of items to skip
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds detail about returning a list with optional filtering and pagination, which is consistent and adds value.

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?

A single 9-word sentence that encapsulates the tool's purpose without any extra words. Efficient and front-loaded.

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?

Given 15 parameters and no output schema, the description covers the essential functionality (listing with filters and pagination). It is moderately complete for a read-only list tool with rich annotations.

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 descriptions for all 15 parameters. The description mentions 'optional filtering and pagination' but does not add deeper meaning beyond the schema.

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 tool retrieves all test cases in a project with filtering and pagination. It distinguishes from siblings like 'get_case' (single) and 'create_case' (write).

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?

The description implies usage for listing cases, but does not explicitly state when to use versus alternatives or provide exclusion criteria. No guidance on when not to use.

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