"Scheduler that invokes the agent based on a predefined schedule" matching MCP tools:

• cairo-vestingA

  OpenZeppelin Cairo ContractsA

  Make a vesting smart contract that manages the gradual release of ERC-20 tokens to a designated beneficiary based on a predefined vesting schedule. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.

  ConnectorNo auth

• set_schedule_rulesA

  My TV ChannelA

  Give the channel a durable schedule: fixed slots ("news at 18:00") and dayparts ("no kids content after 22:00"). The scheduler re-honours these on EVERY rebuild, so you set them once instead of babysitting the grid. **Pro tier or higher.** This REPLACES the entire ruleset — send every rule you want, not just new ones. Sending an empty array removes all rules and returns the channel to plain weighted-random. Validate first with validate_schedule_rules. Rule shapes: time_slot {rule_type:'time_slot', start_time:'18:00', end_time?:'21:00', days_mask:127, selector_type:'asset'|'tag'|'playlist', selector_value:<id|tag|[ids]>, priority?:0} daypart_weight {rule_type:'daypart_weight', start_time:'22:00', end_time:'06:00', days_mask:127, selector_type:'asset'|'tag', selector_value:..., weight_multiplier:0-10} days_mask is a bitmask: bit0=Mon … bit6=Sun. 127=daily, 31=Mon-Fri, 96=weekend. end_time on a time_slot makes it a BLOCK that keeps drawing from the selector until that time — that is how you get 'cartoons 06:00-09:00' rather than one cartoon. selector_type 'playlist' with an array of asset ids plays them IN ORDER. weight_multiplier 0 removes matching assets from that window entirely. Set `timezone` (IANA) or the times mean UTC, which is almost never what the owner meant. Slots start ON-OR-AFTER their time: the programme running into a slot is never cut short, so an 18:00 slot may begin at 18:02. That is intended.

  Connector

  Destructive

  No auth

• create_scheduleA

  TessryxA

  Schedule authoring — create a BRAND-NEW schedule (mints the schedule + its version 1). The definition names a workflow (versioned-slug ref, published/latest), a recurrence (EITHER a 5-field cron + IANA timezone, OR an 'every N minutes/hours' interval), and an optional static input bound as the workflow's $input on every fire; fetch its JSON Schema with get_schedule_definition_schema and author against it. Pass publish=true to activate it (start firing) in one step, or publish later with publish_schedule. (To add a version to a schedule that already exists, use create_schedule_version.)

  ConnectorOAuth

• save_agentA

  Valuein — SEC EDGAR Fundamentals & Smart-Money DataA

  Create or update a standing agent — a saved {goal + tickers + schedule} that fires either a fixed step recipe (agent_type="workflow", free/deterministic) or an AI-directed team (agent_type="autonomous", charged — settles against the owner's BYO key first, falling back to the managed wallet only if funded). Upsert semantics: omit `agent_id` to CREATE a new agent; pass an existing `agent_id` to UPDATE it. There is no separate update_agent — this does both, matching save_watchlist/save_thesis's house style. `agent_type` is STRUCTURAL and immutable: always required, and on an update it is verified against the existing agent before anything is changed — passing a different agent_type than the agent already has is rejected (delete and recreate to change the type). `steps` (an array of {kind:"tool"|"sop", name, args, label?}) is required and non-empty when CREATING an agent_type="workflow" agent, and must be omitted for agent_type="autonomous" (use `managed_model` there instead, itself optional and only valid for agent_type="autonomous"). `when` picks the trigger: "manual" (fires only via run_agent or the Workspace UI) or "schedule" (requires a `schedule` object — cadence "weekly" needs day_of_week, "monthly" needs day_of_month). This tool does NOT itself fire a run — use run_agent for that. Tier: sp500+ (sample rejected).

  ConnectorNo auth

• create_agentA

  WebRun Browser AutomationA

  Create a scheduled agent — a recurring or one-time automation that runs on a timer in a real Chrome browser. Two modes. WORKFLOW MODE: pass workflowId plus a schedule — the platform copies everything else (prompt, starting URL, output contract, model, proxy, policy, files) from the workflow and bakes your variables into the prompt; results and memory stay centralised on the workflow. STANDALONE MODE: omit workflowId and provide name, prompt (a Goal / Ground rules / Stages / Output browsing runbook — see the prompt field description), and a schedule; the connection's environment is used automatically. Ask the user only what it should do and when it should run, in plain language — pick sensible defaults for everything else and state them; never ask about environments or technical settings. Results are delivered to your connected chat and appear in session history.

  ConnectorNo auth

• livereacting_cancel_schedulesA

  LiveReactingA

  Cancel scheduled streams. Give a liveId to cancel that one schedule, or give only a projectId to cancel every schedule on that project. Cancelling cannot be undone; the schedule has to be created again with livereacting_schedule_stream. This only ever touches SCHEDULED streams. It cannot stop a running one -- use livereacting_stop_stream for that. Call this before livereacting_schedule_stream when a project already has schedules, because scheduling refuses to run alongside them.

  Connector

  Destructive

  API key

• check_in_appointmentA

  SimpleDockA

  Record the driver's own update before arrival on a CONFIRMED appointment: ON_TRACK, or RUNNING_LATE with estimatedDelay minutes (e.g. "the driver says he's 30 minutes out and late"). Sets arrivalStatus; the appointment status doesn't change. It never cancels: use cancel_appointment for that. It doesn't start dwell time: when the truck is physically at the dock, use mark_arrived. Fires a webhook; no carrier email. Returns the updated appointment. Requires scope appointments:write (Scheduler role or above).

  ConnectorAPI key

• check_in_appointmentA

  SimpleDockA

  Record the driver's own update before arrival on a CONFIRMED appointment: ON_TRACK, or RUNNING_LATE with estimatedDelay minutes (e.g. "the driver says he's 30 minutes out and late"). Sets arrivalStatus; the appointment status doesn't change. It never cancels: use cancel_appointment for that. It doesn't start dwell time: when the truck is physically at the dock, use mark_arrived. Fires a webhook; no carrier email. Returns the updated appointment. Requires scope appointments:write (Scheduler role or above).

  ConnectorOAuth

• schedule_taskA

  Valuein — SEC EDGAR Fundamentals & Smart-Money DataA

  Defer a follow-up task ("re-check AAPL margin compression in 30 days") for up to 90 days. This is an AGENT-facing primitive — call it mid-conversation/mid-run when you decide something is worth re-checking later; it is NOT a human-authorable "new task" form (use the Workspace's standing-agent scheduler for recurring, human-configured monitoring instead). On wake, an inbox item ALWAYS lands for the owner ("scheduled task due: …"). Optionally pass `context: {managed: true, team_id: "<standing_agent id>"}` to ALSO kick off a managed agent re-run at wake time — this is LIVE: it fires a real run of that standing-agent team, grounded in the saved context. It degrades to the inbox notice alone only if this deploy can't reach the run endpoint (report the actual outcome, never assume). Persisted durably in D1 — never lost on a Worker recycle. Tier: sp500+ (sample rejected).

  ConnectorNo auth

• update_alert_ruleA

  RiusA

  Reconfigure or toggle one alert rule, predefined or custom. `ref` decides which: a kind name (consistent_error_pattern, silent_failure, tool_loop) addresses the predefined rule of that kind; a uuid addresses a custom rule. Get either from list_alert_rules. Only what you pass changes. Turning a rule off stops detection, not just notification — gaps in history are permanent and nothing backfills them. The two rule shapes take DIFFERENT settings, and mixing them is refused with a message naming the right one: * a predefined rule has named integer knobs -> pass `config` * a custom rule has metric thresholds -> pass `rules` (+ `window_minutes`) ref: the rule's kind or uuid. enabled: turn detection on or off. rca_enabled: turn root-cause analysis on or off for this rule. name: rename a custom rule (predefined rules take their name from their kind). config: for a PREDEFINED rule only — its named knobs, e.g. `{"min_errored_spans": 10}`. consistent_error_pattern takes window_minutes, min_errored_spans, min_distinct_traces; silent_failure takes window_minutes; tool_loop takes window_minutes, min_identical_calls. Call describe_alert_catalog for the bounds. rules: for a CUSTOM rule only — replace its thresholds. Replaces the whole list, so pass window_minutes with it. window_minutes: the window. For a custom rule it is part of the replaced config, so pass `rules` too; for a predefined rule put it in `config`. filters: for a CUSTOM rule only — replace its filters. Replaces the whole list. Same shape and the same verbatim-value rule as create_alert_rule. channel_ids: change where the rule delivers. Needs `channels:manage`. An empty list does NOT silence the rule — it re-points it at the region's default webhook. To stop notifications, set enabled to false. workspace: optional workspace id, name, or `org-name/workspace-name` when the same name occurs in two of your orgs (defaults to your default). Example: > Turn off the tool loop alert. ```json { "name": "update_alert_rule", "arguments": { "ref": "tool_loop", "enabled": false } } ``` Example: > Make the error pattern alert less noisy — 10 errors, not 3. ```json { "name": "update_alert_rule", "arguments": { "ref": "consistent_error_pattern", "config": { "min_errored_spans": 10 } } } ```

  Connector

  Destructive

  API key

• bundle_create_export_scheduleA

  gisgpB

  PAID PER DELIVERY (30 credits each time it fires, NOT at creation — free to create/cancel) — the only MCP tool that exposes GISGP's core recurring-export product to agents: creates a schedule that re-exports a FeatureServer layer on its own and POSTs the file straight to your own webhook_url, no email/web UI account needed beyond the API key. Reuses the same scheduler that runs the paid web app's scheduled exports (fires within ~5 min of the due time). format: "csv", "geojson", "shapefile", "kml", or "excel". frequency: "hourly" (top of each hour), "daily" (at run_hour UTC), "weekly" (at run_hour UTC on `weekday`, 0=Monday..6=Sunday), or "monthly" (at run_hour UTC on `monthday`, 1-28). webhook_url: must be a public, reachable HTTPS URL (validated at creation AND at every delivery) — GISGP POSTs a JSON body {schedule_id, format, row_count, filename, delivered_at, data_base64 (or download_url for files >5MB)}. If the wallet lacks 30 credits when a delivery is due, that cycle is silently skipped (schedule stays active, no error surfaced to you) — top up any time at https://gisgp.com/billing/mcp-credits/topup and the next cycle delivers normally. Use estimate_cost or check_wallet_balance to plan ahead. Delete via cancel_export_schedule when no longer needed — an abandoned schedule with an empty wallet just skips forever, but does not charge or error. Requires Authorization: Bearer <api_key>. Returns JSON: {ok, schedule_id, next_run_at}.

  ConnectorNo auth

• create_agentA

  SliqA

  Create a background agent that runs automatically based on triggers. Do NOT create a new agent for follow-ups, event handlers, or scheduled checks that continue an existing agent's work — use `add_trigger` on that agent instead. When the agent matches one of the built-in agent templates — the `template_id` enum lists them — set its `template_id` and seed `workspace.inputs` per that agent's skill guide. The `template_id` runs the template's setup; seed a template's inputs without it and the agent is not fully wired up. If no template fits, omit `template_id` and the agent runs as a general background agent. You MUST call `get_skill_guide('trigger_code')` before writing any trigger's `code` — the qualification rules, sandbox globals, tool surface, and `out` contract live in the skill. `code` runs on the trigger's next firing.

  ConnectorOAuth

• update_scheduleA

  pinbridgeA

  Edit a pending schedule in place: time, board, text or media. Use to fix a wrong run_at, board, title or link on a schedule that has not started publishing, instead of cancel_schedule plus create_schedule; the id and history are kept. Once the schedule has run its pin is published and can no longer be edited; for a failed one use retry_schedule. Pass at least one field. Returns the updated schedule, still in status "scheduled". A new board is preflighted like create_schedule. Fails with not_found for an unknown id, schedule_not_editable (409) once publishing started, with a remediation naming the right tool, validation_error for a past or timezone-less run_at, and sandbox_board_fixed when changing the board of a sandbox schedule.

  Connector

  Destructive

  API key

• create_channelA

  ValetA

  Create a channel on an agent: a cron or heartbeat channel that wakes it on a schedule, a webhook channel that lets callers outside Valet reach it, or an mcp channel that serves it as an MCP server. The channel starts the agent's work; what the agent does when it fires is the prompt file channels/<name>.md in its source. A webhook is signed by a secret you choose, because this never returns a secret value: set it with set_env_vars on the agent first, then pass its name as secret_name. A webhook without secret_name is refused. Creating a channel that already exists with the same kind and settings reports it and changes nothing; different settings are refused, so destroy it first. Slack and Telegram need a browser, so for them this gives the step to take and creates nothing. Requires connecting a Valet account.

  ConnectorNo auth

• reschedule_tableA

  Mostly RightA

  Sets a live table's refresh schedule, or replaces the one it has, without starting a run or fetching anything. A table that went live on its first run has NO schedule yet (get_table shows schedule null, the chat shows "No refresh schedule"): this is the tool that gives it one. When the table's recipe cannot refresh yet, the schedule is HELD rather than applied and the answer carries schedule null: report that, and do not call again. It is also the way to change a cadence without the demote and promote that would reset the table and buy a catch-up refresh. State exactly one of cron (five fields, evaluated in UTC) or interval_seconds (the interval counts from now). rationale records why, kept verbatim beside the schedule. lock: true freezes the schedule so the platform stops adjusting it to the source; leave it out to let it keep learning from there. Pass expected_version from get_table so a table that moved in between is refused rather than overwritten. Example: {"table_id": "…", "cron": "15 6 * * *", "rationale": "The agency publishes the previous day by 06:00 UTC."}. Returns {table_id, dataset_id, promotion_status, schedule, version, dashboard_url}. Only a table that is not live is refused (demoted or never built); a live table with no schedule is exactly what this sets. A schedule that fires more often than the table allows is refused with the floor named. A recorded schedule refreshes a table only where its recipe can refresh — read get_table before saying it does.

  ConnectorNo auth

• auto_schedule_proposalA

  OnplanaB

  PRO+ AI scheduling tool for agents. Proposes a new schedule for a project that fits all tasks before a target deadline while respecting dependencies. Designed for multi-turn agent workflows: call with mode="preview" to generate and present the proposal to the user, then call with mode="apply" once the user confirms. APPLY captures a "Before AI Schedule Proposal" baseline and commits all proposed dates in one atomic operation (requires project Owner or Manager role). Optionally levels resources to avoid overallocation. Cap: 100 tasks. Feature: aiAdvanced (PRO+).

  Connector

  Destructive

  OAuth

• list_timeslotsA

  Tailwind AppA

  Use this when the user asks what their posting schedule looks like, or which times Tailwind recommends: lists the account's smart schedule timeslots. Each slot is a RECURRING WEEKLY time (day of week + HH:MM + timezone), not a concrete date, and this read says nothing about which upcoming occurrences are already taken — use get_schedule for that, which returns dated entries marked open or occupied. This is a read for showing or explaining the recurring schedule, and the place to get the timeslotId that update_timeslot and delete_timeslot need. It is NOT the way to schedule a Pin into it. To place a Pin on the schedule, pass useNextOpenSlot: true to create_post or schedule_post: that resolves the next genuinely open slot and applies the account's Pin Spacing rules for the Pin's destination url. Do not compute an occurrence from these slots and pass it as sendAt — that ignores which slots are occupied and ignores Pin Spacing, so Pins stack up and land off-schedule. If the user did not say which Pinterest account to use and list_accounts returns more than one, ask the user which account to use before calling this — do not choose for them.

  ConnectorOAuth

• schedule_postA

  Tailwind AppA

  Use this when the user wants to schedule or reschedule an existing Pin draft or queued Pin in Tailwind: takes the postId of an existing Pin (from create_post or list_posts) plus exactly ONE of useNextOpenSlot: true or an ISO 8601 sendAt. Prefer useNextOpenSlot whenever the user has not named a specific time — it places the Pin in the account's next open smart schedule slot and applies the account's Pin Spacing rules for the Pin's destination url, which a timestamp you compute yourself cannot. Reserve sendAt for a time the user actually asked for. The Pin must already have title, description, and url set; a draft without a board also needs boardId (numeric ID from list_boards). Pass boardSectionId to schedule it into a Board section — and note that passing boardId on its own clears any section the Pin already had, since a section is only valid on its own Board. Does not work on published Pins. A draft exists only in Tailwind, not on Pinterest, until this step: scheduling is what puts it into Tailwind's publishing flow. Moving a draft onto the schedule is the charged step: one Pin credit on modular billing with Publishing access, whether subscribed or granted, though winback plans schedule without charge and modular accounts without Publishing draw on a free-trial allowance; legacy and Shopify accounts spend no credits and count it against the plan's post limit instead. Rescheduling a Pin that is already queued costs nothing on any of them. To create and schedule a new Pin in one step, use create_post instead. To take a queued Pin off the schedule and back to draft, use unschedule_post. If the user did not say which Pinterest account to use and list_accounts returns more than one, ask the user which account to use before calling this — do not choose for them.

  Connector

  Destructive

  OAuth

• build_cronA

  Cron TranslatorA

  Convert an English schedule description into a standard five-field cron expression, then explain and validate the result. Use this when a user describes a schedule in words and needs the expression. This is a RULE-BASED converter, not a language model: it handles a fixed grammar and returns an error listing the supported phrasings when a phrase falls outside it. That refusal is deliberate — a plausible-looking wrong schedule is worse than no answer. If a phrase is rejected, rephrase it into one of the supported shapes and call again. Returns the expression, which rule matched, any words the rules did not use (check these — leftover words may mean the phrase was misread), the English description of the result, warnings, and the next run times.

  ConnectorNo auth

• analyze-seo-keywordsA

  GigSoul x402A

  Suggest the top 10 SEO keywords for a topic with estimated relative search volume and difficulty. Use for early keyword ideation and content planning. Based on model training knowledge, not a live lookup; figures are estimates. Not live keyword-tool data; validate volumes in an SEO tool before committing budget. For a posting schedule, use generate-content-calendar. Pay-per-call: $0.04 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.

  ConnectorNo auth

• kenwea.agent.sendHeartbeatA

  Kenwea — Sandbox Attestation & Agent MarketplaceA

  Record that this agent is alive. Takes no arguments, returns status accepted, and only updates your last-seen time, which your operator sees. It moves no money and changes nothing else, so repeating it is harmless; call it on a schedule while you run. It checks nothing: for platform load use kenwea.scale.getStatus, for a job you started use kenwea.jobs.getStatus.

  ConnectorNo auth