Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Create scheduled run

create_scheduled_run
Destructive

Creates a recurring evaluation schedule from a run template, keeping it disabled by default unless explicitly enabled to avoid unintended external evaluation activity and costs.

Instructions

Create a recurring evaluation schedule from a run template. New schedules remain disabled unless enabled is explicitly true; enabling can trigger future external evaluation activity and costs.

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": {
      "display_name": "<display_name>",
      "run_template_id": "<run_template_id>",
      "schedule_expression": "<schedule_expression>"
    },
    "name": "create_scheduled_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNoWhether to activate the schedule immediately. Defaults to false.
display_nameYesDisplay name for the scheduled run.
run_template_idYesRun template executed by the schedule.
schedule_timezoneNoTimezone for cron schedules, such as UTC or America/Los_Angeles.
schedule_expressionYesAWS-style rate(...) or cron(...) schedule expression.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.5.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / display_name
      Added value: +{
      +  "description": "Display name for the scheduled run.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / enabled
      Added value: +{
      +  "description": "Whether to activate the schedule immediately. Defaults to false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / run_template_id
      Added value: +{
      +  "description": "Run template executed by the schedule.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9_-]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / schedule_expression
      Added value: +{
      +  "description": "AWS-style rate(...) or cron(...) schedule expression.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "pattern": "^(?:rate|cron)\\(.+\\)$",
      +  "type": "string"
      +}
    • addedInput schema / properties / schedule_timezone
      Added value: +{
      +  "description": "Timezone for cron schedules, such as UTC or America/Los_Angeles.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9._+-]+(?:\\/[A-Za-z0-9._+-]+)*$",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "display_name",
      +  "run_template_id",
      +  "schedule_expression"
      +]
  2. Addedv0.4.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds genuinely new behavior: schedules are inert by default, and enabling one causes future external evaluation activity with associated costs. That cost/external-side-effect disclosure is exactly the kind of context annotations cannot express. It stops short of explaining why the tool is flagged destructive or what is created.

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, zero filler, and the most consequential fact (disabled-by-default, enabling costs money) is front-loaded. Nothing could be removed without losing signal.

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 five-parameter, fully-documented creation tool with no output schema, the description covers the state it leaves behind and the side effects of activation. It omits what is returned (e.g. a schedule ID) and any permission requirements, which are minor gaps given the rich schema.

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 coverage is 100%, so all five parameters are self-documented, which sets the baseline at 3. The description restates the enabled default (already in the schema) and only adds the cost consequence of enabling. It says nothing about schedule_expression syntax or timezone behavior beyond the schema.

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 ('Create a recurring evaluation schedule from a run template'), which is enough to separate it from list_scheduled_runs, update_scheduled_run and get_scheduled_run. It does not, however, contrast itself with create_run, the one-off counterpart an agent could easily confuse it with.

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 can infer this is the setup step before update_scheduled_run or list_scheduled_runs, and that the schedule starts disabled. There is no explicit 'use this instead of X when Y' routing and no mention of prerequisites such as the run template needing to exist.

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