Skip to main content
Glama
Sign In

Fastero

by com.fastero
OverviewDiscussionsAdmin

Set Python schedule

fastero_set_python_schedule
DestructiveIdempotent

Run a Python entrypoint repeatedly on a cron timetable, or change the one it has: an entrypoint has one schedule, and calling again replaces its cron and whether it is on. The cron expression takes 5 fields (minute hour day-of-month month day-of-week) or 6 with leading seconds, and runs in UTC — there is no per-schedule timezone; an expression the scheduler cannot run is refused. A scheduled run cannot be given parameters: it runs the entrypoint as it stands. Each run uses compute, and a failed one is reported to you by email and in the app. The entrypoint id comes from fastero_ensure_python_entrypoint or fastero_get_python_project. With emails or slackChannel, each successful scheduled run also sends the pictures it saved in outputs/ (PNG, JPEG, GIF or WebP) there; a run started by hand sends none. Left out, they stay as they are. Returns ok, triggerId, schedule (the cron as stored), and emails and slackChannel when set. It is the trigger py::, which fastero_list_triggers shows and fastero_disable_trigger pauses. To run once now, fastero_run_python_project; a notebook is scheduled with fastero_schedule_notebook. Owners, admins and editors of the project can set it.

Input Schema

NameRequiredDescriptionDefault
emailsNoWho is emailed the pictures: up to 20 addresses, each belonging to a member of this organisation; an address outside it is refused. An empty list stops the emails.
enabledNoWhether the schedule starts running now. Defaults to true; pass false to create it paused.
scheduleYesCron expression in UTC, 5 or 6 fields. '0 9 * * 1' is 09:00 UTC each Monday. A 4-field value is read as day-of-week omitted.
projectIdYesThe project’s id, from fastero_list_projects.
entrypointIdYesThe entrypoint to run, e.g. 'main'. Returned by fastero_ensure_python_entrypoint.
slackChannelNoA Slack channel to post the pictures to, by name or id, which Fastero must be in: type /invite @Fastero there first. Slack must be connected in Fastero. '' stops the posts.
pythonProjectIdYesA Python project’s id, from fastero_list_python_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / emails
      Added value: +{
+  "description": "Who is emailed the pictures: up to 20 addresses, each belonging to a member of this organisation; an address outside it is refused. An empty list stops the emails.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / slackChannel
      Added value: +{
+  "description": "A Slack channel to post the pictures to, by name or id, which Fastero must be in: type /invite @Fastero there first. Slack must be connected in Fastero. '' stops the posts.",
+  "type": "string"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (idempotentHint/destructiveHint): one schedule per entrypoint, a repeat call overwrites cron and enabled state, no per-schedule timezone, invalid cron rejected, scheduled runs take no parameters, compute is consumed per run, failures are emailed and surfaced in the app, and omitting emails/slackChannel leaves existing values untouched. Annotations alone would not tell an agent any of this.

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?

Dense but front-loaded: the core action and its overwrite semantics come first, then cron rules, then notification behavior, then id derivation and alternatives. Nearly every clause carries operational information; only the trailing permission sentence could be trimmed slightly.

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?

For a 7-parameter mutation tool with no output schema, the description supplies the return shape (ok, triggerId, schedule, emails, slackChannel), the trigger identifier format, error/refusal behavior, and permission requirements. Nothing an agent needs to invoke it safely is missing.

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 adds real semantics on top: the cron field count/UTC interpretation and refusal behavior, the fact that a scheduled run cannot be parameterized, and the crucial rule that omitted emails/slackChannel are preserved rather than cleared. That omission rule is genuinely beyond what the schema says.

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?

Opens with a specific verb and resource: run a Python entrypoint repeatedly on a cron timetable or replace its existing schedule. It explicitly contrasts with fastero_run_python_project (run once) and fastero_schedule_notebook (notebooks), so an agent can separate it from the closest siblings without inspecting schemas.

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?

Names concrete alternatives and the condition that selects each: fastero_run_python_project for a single run, fastero_schedule_notebook for notebooks, fastero_disable_trigger to pause, fastero_list_triggers to inspect. It also states where the required ids come from (fastero_ensure_python_entrypoint, fastero_get_python_project) and which roles may call it.

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

All Fastero toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources