Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Get test set

get_test_set
Read-onlyIdempotent

Retrieve a test set's display name, description, and test case count by its unique ID to inspect evaluation data before running tests.

Instructions

Get test set details: display_name, description, and test case count.

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": {
      "test_set_id": "<test_set_id>"
    },
    "name": "get_test_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_set_idYesThe unique ID of the test set to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed3 schema fields changedv0.4.1
    • changedInput schema / properties / test_set_id / description
      Previous value: -"The unique ID of the test set to retrieve. Get this from list_test_sets."New value: +"The unique ID of the test set to retrieve."
    • addedInput schema / properties / test_set_id / maxLength
      Added value: +128
    • addedInput schema / properties / test_set_id / pattern
      Added value: +"^[A-Za-z0-9_-]+$"
  3. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds return-content context (display_name, description, test case count), but says nothing about behavior on a missing/invalid ID or any other runtime trait.

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?

One short, front-loaded sentence naming the resource and the notable returned fields; nothing is wasted. It is arguably too terse rather than padded, but structurally sound.

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 usefully enumerates the key return values, and the read-only semantics come from annotations. What remains missing is only the sibling relationship (list_test_sets vs. this single-item fetch) and error behavior.

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% and the single test_set_id parameter is documented in the schema with pattern and length constraints. The description adds no format or lookup semantics beyond what the schema already provides, so 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?

States a specific verb and resource ('Get test set details') and enumerates the fields returned, which clarifies what the tool yields. It doesn't explicitly contrast with the sibling list_test_sets, but 'test set details' plus the required test_set_id makes the single-resource lookup clear enough.

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?

No when-to-use or when-not-to-use guidance is given. The agent must infer that this fetches one test set by ID versus list_test_sets for enumeration; the description never says so.

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