Skip to main content
Glama

BriefMe

by us.briefme
OverviewDiscussionsAdmin

Create a meeting agenda

create_agenda

Creates a timed meeting agenda — a shareable countdown timer that walks attendees through timeboxed topics in sync. Use when the user wants a meeting timer, timeboxes, a run of show, a workshop or standup schedule, or to keep a meeting on time. Not for calendar scheduling or note-taking, and a two-item chat needs no timer.

Returns share_token (what later calls take), share_url (the read-only live timer for attendees, safe to post anywhere) and edit_url (the private control page: start, pause, advance and finish the meeting, and edit blocks by hand). Without a linked BriefMe account it also returns edit_token, which later calls take instead of an account. The user needs both links.

When the blocks depart from BriefMe's standard shape — an opening, a wrap-up, planned breaks — the result also carries structure_suggestions, each naming the block to add and its length; add_block and reorder_blocks apply them.

Block durations add up to the meeting length; when none is given, 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 wall-sized countdown, so six words or fewer read best; a description is useful only when the title alone is ambiguous.

Include the opening, the wrap-up and any planned break in this first call: every change afterwards is a separate confirmation for the user.

Agendas expire after 7 days and cannot be recovered afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort name for the meeting, e.g. "Weekly engineering sync".
blocksYesThe agenda blocks, in the order they will run.
languageNoThe user's conversation language as a two-letter ISO 639-1 code (e.g. 'de'). Localizes the standard block titles quoted in structure_suggestions. Unsupported values fall back to English. Defaults to the conversation locale the client sends (openai/locale) when omitted.
idempotency_keyNoOptional. Re-issuing a call with the same key and the same arguments returns the original result instead of repeating the change — send the same key when re-issuing a request whose response was lost. A fresh UUID per call works well; only a retry repeats one.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
blocksYesThe blocks in the order they run.
edit_urlYesThe private control page for running the meeting; not for a shared channel.
share_urlYesThe read-only agenda with the live timer; safe to give to attendees.
edit_tokenNoWhat later anonymous calls take. Absent when the agenda is saved to a linked account.
expires_atYesISO 8601. null when the agenda is saved to an account and does not expire.
share_tokenYesThe agenda's public identifier; what every tool takes as share_token.
instructionsYesWhat the user needs from this result.
total_secondsYesSum of every block's duration_seconds.
structure_suggestionsNoPresent only when the agenda lacks an opening, a closing or a required break; add_block and reorder_blocks apply it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional. Re-issuing a call with the same key and the same arguments returns the original result instead of repeating the change — send the same key when re-issuing a request whose response was lost. A fresh UUID per call works well; only a retry repeats one.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / language / description
      Previous value: -"The user's conversation language as a two-letter ISO 639-1 code (e.g. 'de'). Localizes the standard block titles quoted in structure_suggestions. Unsupported values fall back to English."New value: +"The user's conversation language as a two-letter ISO 639-1 code (e.g. 'de'). Localizes the standard block titles quoted in structure_suggestions. Unsupported values fall back to English. Defaults to the conversation locale the client sends (openai/locale) when omitted."
    • changedOutput schema / properties / blocks / items / properties / block_type / description
      Previous value: -"Internal classification; never mention it to the user."New value: +"Internal classification; appears on no BriefMe page."
    • changedOutput schema / properties / edit_token / description
      Previous value: -"What every other tool takes. Keep it for the rest of the conversation."New value: +"What later anonymous calls take. Absent when the agenda is saved to a linked account."
    • changedOutput schema / properties / edit_url / description
      Previous value: -"The user's private control page. Give it to the user; never post it anywhere shared."New value: +"The private control page for running the meeting; not for a shared channel."
    • changedOutput schema / properties / instructions / description
      Previous value: -"Read this first: how to reply to the user."New value: +"What the user needs from this result."
    • addedOutput schema / properties / share_token
      Added value: +{
+  "description": "The agenda's public identifier; what every tool takes as share_token.",
+  "type": "string"
+}
    • changedOutput schema / properties / structure_suggestions / description
      Previous value: -"Present only when the agenda lacks an opening, a closing or a required break. Apply with add_block and reorder_blocks before replying."New value: +"Present only when the agenda lacks an opening, a closing or a required break; add_block and reorder_blocks apply it."
    • removedOutput schema / properties / upgrade_hint
      Removed value: -{
-  "description": "Present only on a free-tier agenda.",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "instructions",
-  "edit_url",
-  "edit_token",
-  "title",
-  "total_seconds",
-  "expires_at",
-  "share_url",
-  "blocks"
-]New value: +[
+  "instructions",
+  "edit_url",
+  "title",
+  "total_seconds",
+  "expires_at",
+  "share_token",
+  "share_url",
+  "blocks"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / blocks / items / properties / block_type / description
      Previous value: -"Internal classification for analysis — infer it from the content; never mention it to the user."New value: +"Internal classification for aggregate analysis, inferred from the content; shown on no BriefMe page."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "blocks": {
+      "description": "The blocks in the order they run.",
+      "items": {
+        "properties": {
+          "block_type": {
+            "description": "Internal classification; never mention it to the user.",
+            "enum": [
+              "standup",
+              "discussion",
+              "decision",
+              "q_and_a",
+              "break",
+              "opening",
+              "closing",
+              "other",
+              null
+            ],
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "duration_seconds": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Stable 8-letter id: what update_block, remove_block, reorder_blocks and after_block_id take.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "duration_seconds",
+          "block_type",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "edit_token": {
+      "description": "What every other tool takes. Keep it for the rest of the conversation.",
+      "type": "string"
+    },
+    "edit_url": {
+      "description": "The user's private control page. Give it to the user; never post it anywhere shared.",
+      "format": "uri",
+      "type": "string"
+    },
+    "expires_at": {
+      "description": "ISO 8601. null when the agenda is saved to an account and does not expire.",
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "instructions": {
+      "description": "Read this first: how to reply to the user.",
+      "type": "string"
+    },
+    "share_url": {
+      "description": "The read-only agenda with the live timer; safe to give to attendees.",
+      "format": "uri",
+      "type": "string"
+    },
+    "structure_suggestions": {
+      "description": "Present only when the agenda lacks an opening, a closing or a required break. Apply with add_block and reorder_blocks before replying.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    },
+    "total_seconds": {
+      "description": "Sum of every block's duration_seconds.",
+      "type": "integer"
+    },
+    "upgrade_hint": {
+      "description": "Present only on a free-tier agenda.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "instructions",
+    "edit_url",
+    "edit_token",
+    "title",
+    "total_seconds",
+    "expires_at",
+    "share_url",
+    "blocks"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover safety flags; the description supplies the substantive behavior: the four return artifacts (share_token, share_url, edit_url, edit_token), what each is safe for, the linked-account vs. anonymous distinction, the 7-day expiry with no recovery, and the operational rule that opening/wrap-up/breaks must go in this first call because later edits cost a separate confirmation. That is well beyond what structured fields disclose.

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 purpose and usage, then returns, then composition guidance, then the expiry caveat. Dense but nearly every sentence carries non-redundant information; it is longer than typical, though the length is justified by the tool's complexity.

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 creation tool with a mutation annotation profile, an output schema, and 100% param coverage, this description closes every gap an agent needs: what it returns, how to compose blocks, expiry risk, and the confirm-cost of subsequent edits. Nothing material is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real interpretive value: default meeting lengths by type (standup ~15, 1:1 ~30, planning 60-90), typical block count of three to eight, and a six-word title heuristic for readability on a wall-sized countdown. These are heuristics the schema cannot express.

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?

'Creates a timed meeting agenda' pairs a specific verb with a specific resource, and the elaboration of what that artifact is (shareable countdown timer, timeboxed topics in sync) makes it instantly distinguishable from siblings like add_block or update_agenda. No ambiguity about what is produced.

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

Usage Guidelines5/5

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

Explicit trigger list ('meeting timer, timeboxes, a run of show, workshop or standup schedule, or to keep a meeting on time') plus explicit exclusions ('Not for calendar scheduling or note-taking, and a two-item chat needs no timer'). This is the when/when-not/alternatives pattern in full.

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

All BriefMe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources