Runlater

This connector has been deprecated

Duplicate

set_wake

Have AgentLater start you when your inbox gets something, instead of waiting for someone to open a session. Give the https:// URL that starts an agent run (a routine or workflow trigger, a chat webhook, your own server) and any headers it needs, such as Authorization. AgentLater POSTs {"event": "inbox.unread", "project_id", "unread"}, signed like any delivery, and nothing else: read the events with read_inbox. At most one wake per debounce (default 15m), so a burst of results starts you once; a wake that would find nothing unread is dropped. Each wake costs one delivery attempt. After 3 wakes in a row fail it turns itself off (wake.state: disabled) and adds a wake.disabled event to the inbox; call set_wake again to turn it back on. Calling again replaces the URL, headers and debounce. get_project shows it.

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": {
      "url": "<url>"
    },
    "name": "set_wake"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	https:// URL on a public domain name that starts an agent run.
`headers`	No	Headers to send on every wake, e.g. Authorization. Same rules as schedule_http. Values are never shown again. A header value may use {{secret:NAME}} (see set_secret); AgentLater fills it in only when sending, to hosts the secret allows.
`debounce`	No	At most one wake per this long, from "1m" to "24h".	15m

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / headers / description

Previous value: -"Headers to send on every wake, e.g. Authorization. Same rules as schedule_http. Values are never shown again. A header value may use {{secret:NAME}} (see set_secret); RunLater fills it in only when sending, to hosts the secret allows."New value: +"Headers to send on every wake, e.g. Authorization. Same rules as schedule_http. Values are never shown again. A header value may use {{secret:NAME}} (see set_secret); AgentLater fills it in only when sending, to hosts the secret allows."

First observedNov 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does: exact POST body, request signing, debounce collapsing of bursts, dropping wakes that would find nothing unread, delivery-attempt cost, and automatic self-disable after 3 consecutive failures with a wake.disabled inbox event. These are exactly the failure and quota behaviors an agent cannot infer from the schema.

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?

Front-loaded with the purpose before the mechanics, and every sentence conveys distinct operational information. The middle section is dense with parentheticals and clause stacking, which slightly slows scanning but wastes no content.

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 3-parameter mutation tool with no annotations and no output schema, the description covers triggering, payload, dedupe, cost, failure and recovery behavior, which is everything needed to call it correctly and interpret its effects.

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 description coverage is 100%, so baseline is 3, but the description adds replacement semantics ('Calling again replaces the URL, headers and debounce') and that headers are needed for auth (Authorization), which is persistence/idempotency meaning not present in the schema. Minor overlap with the schema's {{secret:NAME}} documentation keeps it from a 5.

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?

States a specific verb and resource — 'Have AgentLater start you when your inbox gets something' — and immediately contrasts it with the passive alternative ('instead of waiting for someone to open a session'). It also disambiguates from read_inbox, which is the sibling an agent might otherwise reach for.

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?

Gives a clear selection context (inbox-driven auto-start vs. polling/waiting) and points to read_inbox for reading the resulting events, plus explicit re-enable/replace semantics ('call set_wake again to turn it back on'). It does not compare against potentially overlapping setup tools like create_hook or watch_http, so the alternative routing is incomplete.

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

All Runlater 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?