Skip to main content
Glama

BriefMe

by us.briefme
OverviewDiscussionsAdmin

Read a meeting agenda

get_agenda
Read-onlyIdempotent

Reads back the current state of an agenda, including the id of every block. Needed when block ids are unknown — for example at the start of a new conversation; after any BriefMe mutation the current state is already in hand.

Identifies the agenda by share_token for an agenda saved to a linked BriefMe account, or by the edit_token create_agenda returned, which authorizes on its own. A share link alone does not open an agenda for editing: get_shared_agenda reads the public agenda behind one, without edit access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edit_tokenNoThe latest edit_token (from create_agenda, or rotate_edit_token after a rotation). Authorizes on its own; needed unless the agenda is saved to a linked account.
share_tokenNoAgenda id (from create_agenda or list_agendas). Required with a linked account, optional beside edit_token.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
blocksYesThe blocks in the order they run.
share_urlYesThe read-only agenda with the live timer; safe to give to attendees.
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.
total_secondsYesSum of every block's duration_seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / edit_token / description
      Previous value: -"The edit_token returned by create_agenda."New value: +"The latest edit_token (from create_agenda, or rotate_edit_token after a rotation). Authorizes on its own; needed unless the agenda is saved to a linked account."
    • addedInput schema / properties / share_token
      Added value: +{
+  "description": "Agenda id (from create_agenda or list_agendas). Required with a linked account, optional beside edit_token.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "edit_token"
-]
    • 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."
    • addedOutput schema / properties / share_token
      Added value: +{
+  "description": "The agenda's public identifier; what every tool takes as share_token.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "title",
-  "total_seconds",
-  "expires_at",
-  "share_url",
-  "blocks"
-]New value: +[
+  "title",
+  "total_seconds",
+  "expires_at",
+  "share_token",
+  "share_url",
+  "blocks"
+]
  2. Changed1 schema field changed
    • 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"
+    },
+    "expires_at": {
+      "description": "ISO 8601. null when the agenda is saved to an account and does not expire.",
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "share_url": {
+      "description": "The read-only agenda with the live timer; safe to give to attendees.",
+      "format": "uri",
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "total_seconds": {
+      "description": "Sum of every block's duration_seconds.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "title",
+    "total_seconds",
+    "expires_at",
+    "share_url",
+    "blocks"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, non-destructive, so the safety profile is covered. The description earns credit beyond that by disclosing auth semantics: the edit_token 'authorizes on its own', a share token is required with a linked account, and a share link alone does NOT grant edit access. It stops short of return-format or pagination detail, but the token model is the behavior an agent actually needs here.

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 the core purpose and the block-id rationale in the first sentence, then moves to identification/auth. The second paragraph is dense and reads a bit tightly, but every sentence carries a distinct constraint (the edit-vs-read distinction) rather than filler.

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?

An output schema exists, so return values need no explanation, and the description still tells the agent the payload contains block ids. Combined with when-to-use, when-not, and both identification paths, nothing needed to call this correctly 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. The description goes further by explaining the relationship between the two tokens — either a share_token for a linked account, or an edit_token that authorizes standalone — which the per-field schema text does not fully convey on its own.

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 and resource ('Reads back the current state of an agenda, including the id of every block') and names the sibling it is not, get_shared_agenda. An agent can distinguish it from get_shared_agenda, list_agendas, and the mutation tools 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?

Explicitly states when to call it ('Needed when block ids are unknown — for example at the start of a new conversation') and when not to ('after any BriefMe mutation the current state is already in hand'), and routes edit-access reads to get_shared_agenda. When/when-not/alternative are all present.

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