Connection check
verified live · 26h ago
agenda-timer
Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.
Tools
7
GitHub stars
—
Installs / wk
—
Licence
—
Transport
streamable-http
Last checked
26h ago
Tools & capabilities
7 toolsRead from the running server on 26h ago.
add_block
title*block_type*edit_token*descriptionafter_block_idduration_seconds*
Adds one block to an existing agenda. Appends it to the end, or inserts it directly after after_block_id when you supply one. Adds only — it does not reorder or change any existin… Adds one block to an existing agenda. Appends it to the end, or inserts it directly after after_block_id when you supply one. Adds only — it does not reorder or change any existing block. Returns the full updated agenda, so you do not need to call get_agenda afterwards.
create_agenda
title*blocks*language
Creates a timed meeting agenda and returns the links that run it. Always reply to the user with BOTH links it returns. edit_url is the user's private control page — the only place… Creates a timed meeting agenda and returns the links that run it. Always reply to the user with BOTH links it returns. edit_url is the user's private control page — the only place the meeting can be started, paused, advanced and finished; a user who is not given it cannot run their meeting. It embeds the edit token on purpose: showing it to the user is required, and the one thing to avoid is posting it anywhere shared. The edit page also lets the owner add, change, remove and reorder blocks in the browser. share_url opens the read-only agenda with the live timer — safe to paste into an invite or a channel; attendees open it to follow along. edit_token is what every other BriefMe tool takes; keep it for the rest of the conversation, it is the only way back into this agenda. Durations: make the block durations add up to the meeting length the user asked for. If they did not give one, infer it — a standup is about 15 minutes, a 1:1 about 30, sprint planning 60 to 90. Most agendas are three to eight blocks. Titles are read off a countdown screen, so keep them to six words or fewer, active and scannable. Add a description only when the title alone is ambiguous. Structure every agenda by the rule below. Agendas expire after 7 days and cannot be recovered afterwards. - Open every agenda with a short welcome / check-in block ("Welcome & check-in", block_type opening): about 5% of the meeting, 1–10 minutes. End it with a wrap-up block for recap, next steps and good-byes ("Wrap-up & close", block_type closing): about 10% of the meeting, 2–15 minutes. Both count toward the meeting length. Only meetings under 10 minutes skip them. - Breaks ("Break", block_type break): none under 100 minutes; one from 100 minutes, two from 181, three from 271, four from 361, five from 451 — roughly one per 90 minutes of work, never leaving a stretch shorter than 45 minutes on either side. Each break is 10 minutes and comes out of the meeting length. Space them evenly and put each at the nearest block boundary: a 2-hour meeting gets one break at about 55 minutes. - For meetings of 5 hours or more, make the break nearest midday a 30–45-minute meal break if the start time makes that fit.
get_agenda
read-only
edit_token*
Reads back the current state of an agenda, including the id of every block. Use this when you need block ids you do not already have — for example at the start of a new conversati… Reads back the current state of an agenda, including the id of every block. Use this when you need block ids you do not already have — for example at the start of a new conversation where the user has pasted an edit token. After any BriefMe mutation you already hold current state, so you do not need to call this again. Requires edit_token — a share link or share URL cannot be used here. If the user has only the share link, this agenda cannot be read or edited through this tool; tell them that and offer to create a new one instead.
remove_block
can modify data
block_id*edit_token*
Removes one block from an agenda. The remaining blocks keep their ids and their order. An agenda must keep at least one block, so this fails on the last one. Removing a block shor… Removes one block from an agenda. The remaining blocks keep their ids and their order. An agenda must keep at least one block, so this fails on the last one. Removing a block shortens the meeting — it does not redistribute that time to the other blocks. Returns the full updated agenda.
reorder_blocks
block_ids*edit_token*
Puts the agenda's blocks into the order you give. block_ids must contain every current block id exactly once — none missing, none extra, none repeated. This only reorders: it cann… Puts the agenda's blocks into the order you give. block_ids must contain every current block id exactly once — none missing, none extra, none repeated. This only reorders: it cannot add, remove or edit a block. If you are unsure of the current ids, call get_agenda first. Returns the full updated agenda.
update_agenda
title*edit_token*
Changes the agenda's title. Does not touch any block — use the block tools for those. Returns the full updated agenda. Changes the agenda's title. Does not touch any block — use the block tools for those. Returns the full updated agenda.
update_block
titleblock_id*block_typeedit_token*descriptionduration_seconds