Skip to main content
Glama

cron_run

Run an existing scheduled task once now through the same job handler used by scheduled fires. This does not change its schedule. The run is recorded in job history with trigger manual. With preview_session_id and preview_id, the task's handler path and payload run once in that exact open preview instead (its code, data, files and mail; one attempt, at most 270 s); the production schedule is only read and never changes.

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": {
      "cron_id": "<cron_id>"
    },
    "name": "cron_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
cron_idYesThe cron ID
preview_idNoExact preview version to run. Requires preview_session_id.
preview_session_idNoOpen preview session to run against. Requires preview_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only cover the safety triad (readOnlyHint=false, idempotentHint=false, destructiveHint=false); the description adds genuinely new behavior: the run is recorded in job history with trigger `manual`, the schedule is untouched, preview mode executes one attempt with a 270 s ceiling, and the production schedule is read-only in that path. It does not say what a caller gets back or what happens on failure/timeout.

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?

Front-loaded with the primary action and its key invariant (schedule unchanged), then the preview variant. The second sentence is dense and packs the timeout, attempt count, and scope into one long clause, which costs a little readability.

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 3-parameter mutation tool with no output schema, the definition covers side effects, history recording, timeout, and preview scoping well. It leaves out return value, error behavior, and any permission requirements, which are the remaining gaps for an agent deciding whether to invoke it.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns more by explaining the pairing semantics of preview_session_id and preview_id and what the run executes against (that exact open preview's code, data, files and mail). The schema alone only says each 'requires' the other.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Run an existing scheduled task once now through the same job handler used by scheduled fires') and immediately distinguishes its effect from other cron operations by noting it does not change the schedule. An agent can tell this apart from cron_update/cron_create without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-use context: fire a schedule immediately without altering it, versus the preview-targeted mode with preview_session_id and preview_id. It does not explicitly name a sibling tool for the adjacent case (editing the schedule), so it stops short of full when-not/alternative guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources