Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

List test sets

list_test_sets
Read-onlyIdempotent

Retrieves test sets with their IDs, names, descriptions, and test case counts, enabling you to browse evaluation scenarios and select the right collection for testing.

Instructions

List test sets (collections of test cases). Each contains evaluation scenarios and returns its ID, name, description, and test case count.

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_sets"
  }
}

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 sets"
    • 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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered and the description only needs to add context. It usefully discloses the returned fields (ID, name, description, test case count), which matters since there is no output schema, but says nothing about pagination behavior or default page sizing.

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 short sentences with no waste; the resource definition is front-loaded and the return-shape detail follows immediately.

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?

Four optional parameters with full schema coverage, annotations covering safety, and a description that partially compensates for the missing output schema by naming returned fields. The remaining gap is pagination semantics—nothing explains how to traverse a multi-page result set—which keeps it from a 5.

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% with all four parameters (filter, order_by, page_size, page_token) documented including examples and defaults. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

Specific verb ("List") plus resource ("test sets"), and it goes further by defining the resource as "collections of test cases" containing evaluation scenarios. It distinguishes itself implicitly from get_test_set by scope, but never names that sibling, so it falls short of the 5 bar.

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?

Usage is implied: an agent reading "List test sets" knows the tool enumerates rather than fetches one. There is no explicit guidance on when to prefer get_test_set or how paging through results works, so it is minimum viable rather than directive.

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