Skip to main content
Glama

mcp_run_action_scheduler

Run due Action Scheduler actions now through its own runner, oldest first, with optional hook or group filters. Returns processed, failed, and remaining counts.

Instructions

Run due (past-due pending) Action Scheduler actions now through Action Scheduler's own runner, oldest first. Optional hook/group filters. Returns processed, failed, remaining. 501 when Action Scheduler is not active. Audit-logged. cvrt-mcp-endpoints 1.16.0+.

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": {
      "site": "<site>"
    },
    "name": "mcp_run_action_scheduler"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNoOnly actions of this hook
siteYesSite id (see list_sites)
groupNoOnly actions of this group
batch_sizeNoHow many due actions to run (1-50, default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does well on several fronts: oldest-first processing order, the returned counters (processed, failed, remaining), the 501 error when Action Scheduler is inactive, and that calls are audit-logged. It still omits what happens to failed actions (retried vs. left pending), whether the operation is repeatable/safe to re-invoke, and any capability or permission prerequisites for a tool that executes writes.

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 and dense: purpose, filters, return values, error mode, and audit note each in a short clause with no filler. The trailing version tag ('cvrt-mcp-endpoints 1.16.0+') is marginal but short enough not to hurt; the abbreviation '501' is terse but unambiguous in context.

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 four-parameter execution tool with no output schema, the description supplies the return shape, ordering guarantee, and error condition, which is more than most. Remaining gaps are failure handling and permission requirements, but nothing essential to selecting and invoking the tool is absent.

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 hook, group, site, and batch_size are already documented, and the description only echoes 'Optional hook/group filters'. It adds no extra semantics such as the batch_size cap/default interaction or how filters combine, so the baseline of 3 applies.

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 due ... Action Scheduler actions now'), plus the mechanism ('through Action Scheduler's own runner') and ordering ('oldest first'), which separates it from the read-only sibling mcp_get_action_scheduler and from a generic mcp_run_cron. An agent can identify the operation without opening the 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?

The trigger condition is explicit: it executes only past-due pending actions, so an agent knows to call it when the queue has backlog rather than to schedule anything new. It does not name any alternative (e.g. reading the queue via mcp_get_action_scheduler first) or say when not to call it, so the exclusion side is missing.

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

Deploy Server

Other Tools