Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Update scheduled run

update_scheduled_run
Destructive

Update selected fields on a recurring evaluation schedule, including timing, timezone, and enabled status, to control future evaluation activity and costs.

Instructions

Update selected fields on one recurring evaluation schedule. Enabling or changing timing 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": {
      "scheduled_run_id": "<scheduled_run_id>"
    },
    "name": "update_scheduled_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
display_nameNo
run_template_idNo
scheduled_run_idYesThe unique ID of the scheduled run to update.
schedule_timezoneNo
schedule_expressionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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: +{
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / enabled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / run_template_id
      Added value: +{
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9_-]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / schedule_expression
      Added value: +{
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "pattern": "^(?:rate|cron)\\(.+\\)$",
      +  "type": "string"
      +}
    • addedInput schema / properties / schedule_timezone
      Added value: +{
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9._+-]+(?:\\/[A-Za-z0-9._+-]+)*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / scheduled_run_id
      Added value: +{
      +  "description": "The unique ID of the scheduled run to update.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9_-]+$",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "scheduled_run_id"
      +]
  2. Addedv0.4.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false, openWorld=true, so the baseline is low. The description adds genuinely new context: that timing/enable changes trigger future external evaluation activity and cost, which an agent cannot infer from the hints alone. It omits what happens to unspecified fields, but the added cost warning is substantive.

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 tight sentences, zero filler, with the mutating scope front-loaded and the risk warning second. Every clause carries information.

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

Completeness3/5

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

The tool is destructive and has no output schema, and the description does address the key risk (external activity/cost). However, with 6 parameters at 17% coverage, an agent still cannot tell what schedule_expression accepts or what changing run_template_id does, leaving a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% (just scheduled_run_id documented), so the description must compensate for five undocumented parameters. It only loosely alludes to 'enabling' and 'timing' (covering enabled and schedule_expression/timezone at best) and says nothing about run_template_id, display_name, or accepted schedule syntax.

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 (update) and resource (recurring evaluation schedule) with the scope 'selected fields', which distinguishes it from create_scheduled_run and get_scheduled_run. It stops short of explicitly naming a sibling, but the intent is unambiguous.

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 second sentence gives a real consequence for enabling or retiming, hinting at when caution is needed, but there is no explicit guidance on when to use this versus create_scheduled_run or how partial updates behave relative to existing configuration.

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