excalibur_resolve_dynamic_block

io.github.lonniev/excalibur-mcp · Verify this server

Start resolving a dynamic post block with an LLM — returns a CLAIM CHECK. A dynamic block's ``prompt`` is run by the model (with web search + web fetch for live data) and woven into the surrounding post ``context`` in the author's ``voice``. The author's instruction governs length — there is no character cap (X supports long-form posts). The operator's LLM key stays in the vault and never leaves the server. Because that work (paginated fetches + generation) can outlast a client timeout, this returns immediately with a **claim check** instead of the text: ``{"success": true, "claim_check": "...", "status": "pending", "poll_after_seconds": N}``. Redeem it with the free companion ``fetch_dynamic_block(claim_check)`` until ``status == "done"`` (then read ``result.text``). (The scheduler resolves blocks directly server-side at fire time and does not use this tool.) Paid: the AI cost is metered as a tollbooth fare on THIS start call, refunded if no LLM key is configured or the job ultimately fails.