Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

List scheduled runs

list_scheduled_runs
Read-onlyIdempotent

List recurring evaluation schedules, filtered by enabled state or run template, and return a bounded page for monitoring upcoming evaluation runs.

Instructions

List recurring evaluation schedules. Results can be filtered by enabled state or run template and are returned as a bounded page.

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

Input Schema

NameRequiredDescriptionDefault
enabledNoFilter scheduled runs by enabled state.
page_sizeNoNumber of scheduled runs to return (1-100, default 50).
page_tokenNoToken for retrieving the next page of scheduled runs.
template_idNoFilter scheduled runs by run template ID.

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that results come back as a bounded page, which hints at pagination behavior, but that is largely redundant with page_size's documented 1-100 maximum and says nothing about default ordering or what happens when page_token is exhausted.

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 short sentences with no filler, the core purpose stated first and the filtering/pagination constraints following. Every clause carries information an agent would otherwise have to guess.

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?

For a zero-required-parameter, non-nested, read-only list tool with 100% schema coverage and full annotations, the description covers purpose, filterability, and bounded paging. With no output schema present, it could say a bit more about the shape of a returned schedule, but nothing essential to correct invocation is 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?

Schema description coverage is 100% and every one of the four parameters carries its own description, including ranges and patterns, so the schema does the heavy lifting. The description only restates the two filter dimensions (enabled, template_id) without adding format or interaction detail, which is the baseline expected when the schema is fully documented.

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?

"List recurring evaluation schedules" gives a specific verb and resource, and the word "recurring" clarifies the resource's semantics beyond the ambiguous name 'scheduled runs'. However, it never explicitly distinguishes itself from its nearest siblings list_runs, get_scheduled_run, or create_scheduled_run, so an agent must infer that this is the bulk listing of schedules.

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?

The description implies usage by naming two filter dimensions (enabled state, run template), which suggests this is the tool for scoped enumeration of schedules. But it offers no explicit when-to-use or when-not guidance and never routes the agent to get_scheduled_run for single-item retrieval or to list_runs for executions, leaving alternative selection to inference.

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