Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Get test case

get_test_case
Read-onlyIdempotent

Retrieve a test case's scenario, expected behaviors, and metadata by ID to inspect evaluation criteria and reuse the case.

Instructions

Get test case details: input_str (the scenario), expected_behaviors, and metadata.

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_case_id": "<test_case_id>"
    },
    "name": "get_test_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_case_idYesThe unique ID of the test case to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / test_case_id / maxLength
      Added value: +128
    • addedInput schema / properties / test_case_id / pattern
      Added value: +"^[A-Za-z0-9_-]+$"
  2. 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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's contribution is limited to naming the return payload shape, which is modest added value rather than rich behavioral disclosure (no auth, rate-limit, or not-found semantics).

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 front-loaded sentence with no filler; the return-field list is packed efficiently. It reads as a fragment rather than a full sentence, but nothing in it wastes tokens.

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 returned fields, and the annotations carry safety semantics. For a one-parameter read-only getter this is nearly sufficient; only not-found/error behavior and sibling disambiguation are missing.

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?

There is a single parameter, test_case_id, and schema coverage is 100% with a pattern, length bounds, and its own description. The description adds nothing beyond the schema — which is the expected baseline when the schema does the work — so a 3 is correct rather than a low score.

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 case) and even enumerates the returned fields (input_str, expected_behaviors, metadata), so the agent knows exactly what comes back. It does not, however, distinguish itself from sibling list_test_cases or get_test_set, leaving the single-vs-many routing to inference.

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 rather than list_test_cases (browse) or get_test_set (parent container). The description gives no prerequisites, no mention of behavior when the ID is unknown, and no alternatives — usage must be inferred entirely from the name.

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