Skip to main content
Glama
Sign In
TestOps MCP Server

TestOps MCP Server

by kirchik95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search-test-cases

Find test cases by AQL queries, filtering by name, tag, status, custom fields, and more.

Instructions

Search test cases using AQL (Allure Query Language). Examples:

  • name ~= "login" (name contains)

  • tag = "smoke" (by tag)

  • automation = true (automated only)

  • status = "Active" (by status)

  • cf["Epic"] = "Auth" (custom field)

  • createdBy = "Ivan" and tag in ["smoke", "regression"] (combinations) Use list-project-custom-fields and list-custom-field-values to discover valid cf names and values.

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": {
      "projectId": "<projectId>"
    },
    "name": "search-test-cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
aqlNoAQL filter expression
rqlNoDeprecated alias for aql
pageNoPage number (0-based)
sizeNoPage size
projectIdYesProject ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. It explains AQL syntax and deprecation of 'rql', but doesn't mention read-only nature, pagination details (0-based page), or authentication needs.

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?

Concise and well-structured: purpose front-loaded, followed by examples, then a helpful tip. No unnecessary verbiage.

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

Completeness3/5

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

No output schema; description doesn't indicate what the tool returns (list of test case objects). Given complexity, more context on return format or limitations would be beneficial.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds significant value by demonstrating AQL syntax and custom field usage, going beyond the schema descriptions.

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 searches test cases using AQL, with specific examples. It distinguishes itself from sibling tools like 'list-test-cases' by focusing on query language-based search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides examples and a tip to use other tools for custom field discovery. However, it doesn't explicitly state when to prefer this over 'list-test-cases' or other simple listing tools.

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

Deploy Server

Other Tools