Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

List test cases

list_test_cases
Read-onlyIdempotent

Retrieve and filter test cases by test set ID to review scenario inputs and expected behaviors. Supports pagination and sorting for organized evaluation.

Instructions

List test cases. Filter by test_set_id. Each has input_str (scenario text or JSON message array) and optional expected_behaviors.

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": "list_test_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoFilter expression (e.g., status="COMPLETED")
order_byNoSort order (e.g., "-create_time" for newest first)
page_sizeNoNumber of results per page (1-100, default 50)
page_tokenNoToken for retrieving the next page of results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed4 schema fields changedv0.4.1
    • addedInput schema / description
      Added value: +"Input for listing test cases. Use filter=\"test_set_id=\\\"abc12345\\\"\" to filter by test set."
    • addedInput schema / properties / filter / maxLength
      Added value: +1000
    • addedInput schema / properties / order_by / maxLength
      Added value: +200
    • addedInput schema / properties / page_token / maxLength
      Added value: +2048
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only, idempotent, non-destructive operation. The description adds useful context by describing item return fields—input_str and optional expected_behaviors—which is valuable because no output schema is provided, though pagination behavior is not described.

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 three short sentences with no wasted text. The core listing purpose and key return fields are 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?

For a read-only list tool with full parameter schema coverage and annotations covering safety, the description is largely complete. It provides partial return-value context even without an output schema, though it does not mention pagination or all fields returned.

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 description coverage is 100%, so all four parameters are already documented in the schema. The description repeats the test_set_id filter hint, but does not add meaning for order_by, page_size, or page_token beyond what the schema already provides.

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 states a specific verb and resource: "List test cases." It also mentions test_set_id filtering and return fields, so the tool is distinguishable from get_test_case, but it does not explicitly contrast itself with siblings such as list_test_sets or get_test_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?

The description implies usage by saying "Filter by test_set_id," but that is also present in the schema. It gives no explicit guidance on when to use this tool instead of get_test_case or how to choose between listing and retrieving a single test case.

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