VibeKit

VibeKit Create Schedule

vibekit_create_schedule

Create a recurring coding task that the AI runs automatically on a cron schedule (e.g. a weekly SEO pass). Use for 'every Monday, do X to my repo' requests.

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": {
      "task": "<task>",
      "repo": "<repo>",
      "cron": "<cron>"
    },
    "name": "vibekit_create_schedule"
  }
}

Input Schema

Name	Required	Description
`cron`	Yes	Cron expression, e.g. '0 9 * * 1' for every Monday at 9am UTC
`name`	No	Friendly name for the schedule (optional)
`repo`	Yes	Repo of one of the user's deployed VibeKit projects, as 'owner/repo' (the repo vibekit_submit_task made). That project's agent runs each time and posts its report in the project chat.
`task`	Yes	What to do on each run, e.g. 'Improve SEO and page speed'

Output Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	The created schedule: id, name, and cron expression.
`error`	No	Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / repo / description

Previous value: -"GitHub repo as 'owner/repo'"New value: +"Repo of one of the user's deployed VibeKit projects, as 'owner/repo' (the repo vibekit_submit_task made). That project's agent runs each time and posts its report in the project chat."

Changed1 schema field changedJul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Result envelope: ok=true with data on success, ok=false with error on failure.",
+  "properties": {
+    "data": {
+      "description": "The created schedule: id, name, and cron expression."
+    },
+    "error": {
+      "description": "Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent create operation. The description adds useful behavioral context by explaining that the AI runs the task automatically on a recurring cron schedule. It does not explain persistence or how schedules are later removed, but the annotations reduce the disclosure burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the core action and mechanism. Every sentence adds useful meaning with no filler.

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?

Given the rich schema, annotations, and output schema, the description covers the essential purpose and usage context. It could do slightly more to mention related management operations or prerequisites, but the necessary calling information is present.

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 the schema already documents all four parameters in detail. The description's 'every Monday, do X to my repo' phrasing loosely maps to cron, task, and repo, but it adds no parameter syntax or constraints beyond what the schema provides.

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?

The description states a precise verb and resource: 'Create a recurring coding task.' It also names the execution mechanism ('cron schedule') and gives a concrete example, making the recurring nature clear enough to distinguish it from one-off task submission siblings.

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?

It gives a clear trigger condition: use for requests like 'every Monday, do X to my repo.' However, it does not explicitly mention when not to use it or name the sibling alternative for one-off tasks, such as vibekit_submit_task.

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

All VibeKit tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.