Skip to main content
Glama

run_schedule

Triggers a refresh schedule immediately, dispatching ranked source failovers and recording the execution.

Instructions

Run one refresh schedule now (ranked-failover dispatch + execution record).

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": {
      "schedule_id": "<schedule_id>"
    },
    "name": "run_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
schedule_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds one useful side-effect detail ('execution record' is created) and the immediate-dispatch nature of the call, but says nothing about what gets executed, whether the run is async, or how to observe/abort it afterward.

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?

A single front-loaded sentence with the action first and the qualifier second; nothing is redundant. The parenthetical is the only low-value wording, being undefined internal terminology.

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?

An output schema exists, so return values need not be explained, and annotations cover the mutation profile. However, for a non-idempotent dispatch action the definition should indicate where schedule_id comes from (e.g., list_schedules) and whether execution is synchronous, both of which are missing.

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?

There is one parameter with 0% schema description coverage, so the description must carry the burden of explaining schedule_id and does not—it never says what a schedule ID identifies or where to obtain one. With no compensating detail, the parameter's meaning is left to inference from sibling tool names.

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?

Uses a concrete verb ('Run') on a specific resource ('one refresh schedule') and clarifies immediacy with 'now', which separates it from list_schedules, generate_refresh_schedules, and platform_cancel_run. The parenthetical 'ranked-failover dispatch + execution record' is internal jargon that adds little clarity about the action itself.

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

Usage Guidelines2/5

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

The word 'now' implies an on-demand trigger versus a scheduled one, but there is no explicit statement of when to use this instead of alternatives, no prerequisites, and no mention of what to do if a run is already in progress. Guidance is entirely inferred.

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