MCP Server By TestMu AI

Find / Get Test Cases

tm_get_test_cases

Read-only

Find test cases in a project by filters (folder, priority, automation status, type, tags) and/or search (matches test case ID like TC-123, or title; minimum 3 characters) — returns summaries. Filters combine (AND). Pass case_id instead to get one case's full detail (steps, BDD scenarios, field values).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tm_get_test_cases"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`tags`	No	Filter by tags
`type`	No	Filter by test type (e.g. Functional, Regression, Smoke & Sanity)
`limit`	No	Max results per page
`search`	No	Full-text keyword (min 3 chars)
`case_id`	No	Test case ID (ULID). When given, returns that case's full detail and all other filters are ignored.
`priority`	No	Filter by priority (e.g. Lowest, Low, Medium, High, Highest). A value outside the project's priority list is rejected with the valid values.
`folder_id`	No	Only cases in this folder
`project_id`	No	Project ID (ULID). Required unless case_id is given.
`automation_status`	No	Filter by automation status (e.g. Automated, Not Automated, To Be Automated)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / priority / description

Previous value: -"Filter by priority (e.g. Lowest, Low, Medium, High, Highest)"New value: +"Filter by priority (e.g. Lowest, Low, Medium, High, Highest). A value outside the project's priority list is rejected with the valid values."

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context: results are summaries, the search must be at least 3 characters, filters combine via AND, and case_id silently overrides all other filters. That override behavior is a genuinely useful warning the annotations do not convey.

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?

Two compact sentences, front-loaded with the primary search use case before the single-case alternative. Every clause carries information; no filler or restatement of the title.

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?

With no output schema, the description partly compensates by naming the return shape (summaries vs. steps/BDD scenarios/field values). It omits any mention of pagination behavior despite page/limit parameters, which is the main remaining gap.

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%, so the baseline is 3. The description adds meaning beyond the schema by clarifying what `search` matches (test case ID like TC-123 or title), the AND semantics of filters, and that case_id causes other filters to be ignored — semantics the schema only partially states.

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 names the specific resource (test cases in a project) and the two distinct modes: filtered search returning summaries, and single-case lookup via case_id returning full detail. That distinction lets an agent tell this apart from the sibling list/search tools without opening the schema.

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?

It gives explicit routing within the tool ('Pass case_id instead to get one case's full detail') and states that filters combine with AND. It does not name a sibling tool (e.g. tm_get_test_runs, tm_list_folders) as an alternative, so it stops short of the 5 rubric's explicit alternative naming.

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

All MCP Server By TestMu AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?