Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Create test set

create_test_set

Create and organize evaluation scenarios into test sets with names, descriptions, parameters, and metadata for structured agent testing.

Instructions

Create a test set for organizing evaluation scenarios.

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": {
      "display_name": "<display_name>"
    },
    "name": "create_test_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoURL-friendly identifier (auto-generated if not provided)
parametersNoTest case parameterization (e.g., {"name": ["Alice", "Bob"]})
descriptionNoDescription of the test set
display_nameYesHuman-readable name for the test set
test_set_typeNoType of test set: DEFAULT, SCENARIO, TRANSCRIPT, WORKFLOW
test_set_metadataNoAdditional configuration metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / parameters / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / test_set_metadata / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent creation, so safety is covered. The description adds nothing beyond that — no mention of duplicate-name behavior, whether the returned slug is derived from display_name (schema-only detail), or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the core action front-loaded and no wasted clauses. It is efficient, though its brevity borders on under-specification rather than deliberate compression.

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

Completeness2/5

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

With six parameters, two nested objects, and no output schema, the description leaves the agent without guidance on result shape, required context, or how this fits with test cases and runs. The rich schema helps, but the definition is thin for a tool of this complexity.

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%, including the slug auto-generation note and test_set_type values, so the schema carries the parameter semantics. The description contributes no additional parameter meaning, making the baseline 3 appropriate.

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?

States a specific verb and resource ('Create a test set') plus a purpose ('organizing evaluation scenarios'), which is clearer than the bare title. It does not explicitly differentiate from siblings like create_test_case, so an agent must infer the hierarchy itself.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus create_test_case, create_run, or list_test_sets, and no prerequisites (e.g., needing a parent project or that cases are added afterward). The agent gets only a general purpose, not routing guidance.

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