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 — typically at the start of a new conversation where the user has pasted an edit token; after any BriefMe mutation the current state is already in hand.

Takes edit_token only. A share link or share URL does not open an agenda here: one known only by its share link cannot be read or edited through this connector, only re-created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edit_tokenYesThe edit_token returned by create_agenda.

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.
total_secondsYesSum of every block's duration_seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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 readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description still adds genuine non-structured context: the edit_token is the sole credential, and an agenda known only by its share link is unreachable through this connector (re-create only). It stops short of stating failure modes or error behavior for a bad/rotated token.

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 with the core purpose, then usage triggers, then the credential constraint. Every sentence carries information, though the share-link sentence is wordy ('A share link or share URL does not open an agenda here') and could be tightened.

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; the description instead covers what the agent must know to invoke correctly — trigger conditions, sole-parameter credential, and the share-link exclusion. Nothing material is missing for a one-parameter read 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% and the schema already says edit_token comes from create_agenda, so the baseline is 3. The description adds a real semantic constraint beyond the schema: 'Takes edit_token only' and that share links/share URLs are not accepted as an equivalent credential, which prevents a plausible misuse.

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+resource ('Reads back the current state of an agenda') and even names the payload detail that matters ('including the id of every block'). The framing 'Needed when block ids are unknown' implicitly separates it from the mutating siblings (create_agenda, add_block, update_block), so an agent can route without opening schemas.

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 trigger ('typically at the start of a new conversation where the user has pasted an edit token') and an explicit when-NOT ('after any BriefMe mutation the current state is already in hand'). It also rules out a tempting but invalid alternative: a share link cannot be used to read an agenda here.

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