Bunstation

Create Cloud cron

projects_cloud_cron_create

Create a scheduled job. name is a lowercase DNS label. schedule is a 5-field UTC cron expression, for example */5 * * * *. Source exports default async () => {}. Crons are not called from the website.

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": {
      "project_id": "<project_id>",
      "name": "<name>",
      "schedule": "<schedule>"
    },
    "name": "projects_cloud_cron_create"
  }
}

Input Schema

Name	Required	Description
`env`	No	String map. Do not put these values in public website source.
`name`	Yes	Lowercase DNS label, max 32 characters.
`source`	No	TypeScript source. export default async () => {}.
`schedule`	Yes	5-field UTC cron expression, for example /15 * * * or @daily.
`project_id`	Yes	UUID of a Bunstation project owned by the authenticated user.
`dependencies`	No	String map. Do not put these values in public website source.

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`source`	Yes
`status`	Yes
`enabled`	Yes
`schedule`	Yes
`truncated`	Yes
`function_id`	Yes
`last_run_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds genuinely useful behavior: the schedule is interpreted in UTC, and the source file's expected shape is 'export default async () => {}'. However, it says nothing about what happens on duplicate names, what the created cron state looks like, or whether the job starts running immediately, which is important for a non-idempotent create.

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?

Four short sentences, front-loaded with the purpose and then the key constraints, with essentially no filler. The final sentence about crons not being called from the website is vague enough to feel slightly out of place, but it is not wasteful.

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?

With an output schema present, the description doesn't need to explain return values, and annotations cover the safety profile. It supplies the two non-obvious semantic details (UTC cron format, async default export source shape), though it omits any mention of the env/dependencies maps that the schema flags as sensitive.

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 name format, schedule expression, source, env, and project_id. The description largely restates those (lowercase DNS label, 5-field UTC cron) rather than adding new meaning, and it never mentions the env/dependencies maps. Baseline 3 applies when the schema carries the parameter burden.

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?

The description opens with a specific verb+resource pair, 'Create a scheduled job,' which unambiguously separates this from sibling tools like projects_cloud_cron_get, _run, or _update. It doesn't explicitly name those alternatives, but the create verb plus the tool name makes the scope obvious.

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

Usage Guidelines3/5

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

Usage is only implied: 'Crons are not called from the website' hints at the invocation model but is cryptic and doesn't explain when to choose this tool over projects_cloud_cron_update or _run. No prerequisites (e.g., a project must already exist, cloud must be enabled) or exclusions are stated.

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

All Bunstation 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.

Resources

Need Help?