Skip to main content
Glama

Run schedule now

run_schedule_now
Destructive

Run an existing schedule once, now, and deliver the result to its configured destination exactly as the next scheduled run would: it overwrites the schedule's Google Sheets range or posts to its Slack channel. Use it to test a schedule right after create_schedule, or when someone needs fresh data before the next run. A successful run also clears a failing schedule's retry backoff, so use it to confirm a fix when list_schedules shows a lastError. Does not change the cadence. Returns the spreadsheet URL and written range, or whether the Slack message was delivered. Needs the execute scope and a member role that can edit.

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": {
      "id": "<id>"
    },
    "name": "run_schedule_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSchedule id from list_schedules.

Output Schema

NameRequiredDescriptionDefault
successNo
writtenRangeNoA1 range the export wrote to.
slackDeliveredNo
spreadsheetUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive=false is not the case here (destructiveHint=true), and the description earns its keep by explaining exactly what is destroyed/overwritten: the schedule's Google Sheets range, or a Slack post. It adds non-obvious behavior (clears retry backoff on success) and prerequisites (execute scope, member role that can edit) that annotations cannot express.

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 core action and destination semantics, then usage cases, then side effects and auth. Dense but every clause carries information; the colons and multi-clause sentences make it slightly heavier than it needs to be.

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

Completeness5/5

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

Covers action, side effects, cadence invariance, permissions, and a brief mention of what is returned even though an output schema exists. For a one-parameter mutation tool with openWorld and destructive hints, nothing an agent needs to call it safely 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 coverage is 100% and the single parameter 'id' is already documented as coming from list_schedules, so the schema carries the load. The description reinforces that the schedule must be an existing one but adds no id format or lookup detail beyond the schema. Baseline 3 is appropriate.

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 schedule once, now') and immediately distinguishes itself from the create flow by naming create_schedule and list_schedules as the surrounding siblings. An agent can tell this apart from create_schedule or run_saved_query 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 Guidelines5/5

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

Gives three explicit triggers: test right after create_schedule, get fresh data before the next run, and confirm a fix when list_schedules shows a lastError. It also bounds usage by noting it 'does not change the cadence,' which implicitly excludes it as a rescheduling tool.

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