Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

List run templates

list_run_templates
Read-onlyIdempotent

Retrieve reusable evaluation configurations from your organization, with paginated results and a continuation token for accessing additional pages.

Instructions

List reusable evaluation configurations in the authorized organization. Returns a bounded page and a continuation token when more are available.

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

Input Schema

NameRequiredDescriptionDefault
page_sizeNoNumber of run templates to return (1-100, default 50).
page_tokenNoToken for retrieving the next page of run templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.4.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the operation is read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context by explaining that results are a bounded page with a continuation token for further pages, which is not covered by annotations.

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 sentences, front-loaded with the core action and followed by return behavior. Every sentence adds value with no redundant or filler text.

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

Completeness5/5

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

For a simple read-only list tool with fully documented pagination parameters and annotations covering safety behavior, the description is complete. It supplies organizational scope and pagination behavior, so an agent has everything needed to call it correctly.

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%, so both parameters are fully documented in the schema. The description mentions the bounded page and continuation token concept but adds no syntax, defaults, or constraints beyond what the schema already provides.

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?

The description states a specific verb and resource: listing reusable evaluation configurations (run templates) scoped to the authorized organization. It distinguishes templates from runs and agents by describing them as configurations, though it does not explicitly contrast with sibling listing tools.

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 by the tool name and description, but there is no explicit guidance on when to use this versus alternatives such as list_runs or get_run. No exclusions or prerequisites are stated beyond the organizational scope.

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