BriefMe

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 edit_url (the private control page: start, pause, advance and finish the meeting, and edit blocks by hand), share_url (the read-only live timer for attendees, safe to post anywhere) and edit_token (needed by every other BriefMe tool, and the only way back into this agenda). 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.

Agendas expire after 7 days and cannot be recovered afterwards.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Short name for the meeting, e.g. "Weekly engineering sync".
`blocks`	Yes	The agenda blocks, in the order they will run.
`language`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description
`title`	Yes
`blocks`	Yes	The blocks in the order they run.
`edit_url`	Yes	The user's private control page. Give it to the user; never post it anywhere shared.
`share_url`	Yes	The read-only agenda with the live timer; safe to give to attendees.
`edit_token`	Yes	What every other tool takes. Keep it for the rest of the conversation.
`expires_at`	Yes	ISO 8601. null when the agenda is saved to an account and does not expire.
`instructions`	Yes	Read this first: how to reply to the user.
`upgrade_hint`	No	Present only on a free-tier agenda.
`total_seconds`	Yes	Sum of every block's duration_seconds.
`structure_suggestions`	No	Present only when the agenda lacks an opening, a closing or a required break. Apply with add_block and reorder_blocks before replying.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 11, 2026

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"
+}

First observedSep 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover only the safety profile (not read-only, not idempotent, not destructive). The description adds substantial context: the three return values and their meanings, that edit_token is required by every other BriefMe tool, that structure_suggestions may appear, and that agendas expire after 7 days with no recovery. This is exactly the kind of behavioral detail the annotations cannot convey.

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-loads purpose, then usage, then return values and construction guidance; sentences are dense and informative. It runs long across several paragraphs, but nearly every sentence earns its place by adding operational detail, so only a minor conciseness deduction.

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?

Even though an output schema exists (relieving the description of return-value duties), it still describes the payload, and it covers expiry, follow-up tooling, and block-construction norms. An agent has everything needed to decide, call, and correctly populate this tool.

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 baseline is 3, but the description adds real construction guidance beyond the schema: default durations by meeting type (standup ~15 min, 1:1 ~30, sprint planning 60–90), the 3–8 block norm, the six-word title heuristic, and when a description is warranted. The 'language' parameter is only covered by the schema, keeping this 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 ('Creates') and resource ('timed meeting agenda — a shareable countdown timer that walks attendees through timeboxed topics in sync'). It also explicitly rules out adjacent tasks ('Not for calendar scheduling or note-taking'), letting an agent distinguish this from get_agenda/update_agenda siblings without opening a schema.

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?

Gives an explicit when-to-use list ('meeting timer, timeboxes, a run of show, a workshop or standup schedule'), an explicit when-not ('Not for calendar scheduling or note-taking, and a two-item chat needs no timer'), and names the sibling tools (add_block, reorder_blocks) that apply follow-up changes. Nothing is left to inference.

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

All BriefMe tools Inspect

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

Need Help?