Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Get run

get_run
Read-onlyIdempotent

Retrieve an evaluation run's status and results by run ID, including PENDING/RUNNING/COMPLETED state, completed metrics, and output IDs for transcripts.

Instructions

Get run status/results. Status: PENDING→RUNNING→COMPLETED. Completed runs include metrics (custom per org) and output_ids for transcripts.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe unique ID of the run to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.1
    • changedInput schema / properties / run_id / description
      Previous value: -"The unique ID of the run to retrieve. Get this from list_runs."New value: +"The unique ID of the run to retrieve."
    • addedInput schema / properties / run_id / maxLength
      Added value: +128
    • addedInput schema / properties / run_id / pattern
      Added value: +"^[A-Za-z0-9_-]+$"
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered. The description earns credit by adding value annotations can't: the PENDING→RUNNING→COMPLETED lifecycle and the fact that completed runs carry metrics (custom per org) and output_ids, which tells the agent results may be absent on early polls.

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?

Two short sentences, front-loaded with purpose before the return-shape detail. The lifecycle arrow notation is dense but readable; nothing is wasted, though it could be marginally clearer as prose.

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?

No output schema exists, so the description usefully sketches the return shape (status, metrics, output_ids). Combined with strong annotations, an agent has enough to call it correctly; only the missing guidance on incomplete/unknown runs keeps it below 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?

There is a single parameter at 100% schema coverage, and the schema documents run_id with type, length and pattern. The description adds nothing about run_id beyond what the schema provides, so the baseline of 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 run') plus what it returns: status and results, with metrics and output_ids on completion. It is distinguishable from list_runs by virtue of retrieving a single run, though the description never names siblings explicitly.

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 only implied: an agent infers it should call this when it has a run_id and wants status/results. There is no explicit when-to-use versus list_runs/list_runs filtering, and no mention of error behavior for unknown or not-yet-started IDs.

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