create_agenda
shallowus.briefme/agenda-timer · Verify this server
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.
1 trials · measured 2 days ago
create_agenda scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against us.briefme/agenda-timer, measured 31 Aug 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-08-31 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/65806321-5ddf-4e62-9c62-269e3d7c70b6)