Skip to main content
Glama

BriefMe

by us.briefme
OverviewDiscussionsAdmin

Remove a block

remove_block
DestructiveIdempotent

Removes one block from an agenda. The remaining blocks keep their ids and their order.

An agenda must keep at least one block, so this fails on the last one. Removing a block shortens the meeting — it does not redistribute that time to the other blocks.

Returns the full updated agenda.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesThe id of the block to remove.
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.3/5.0
Behavior5/5

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

Adds substantive behavior beyond the annotations: id stability ('remaining blocks keep their ids and their order'), the invariant that the last block cannot be removed, and the non-obvious fact that the meeting shortens rather than redistributing time. That last point is exactly the kind of side-effect an agent would otherwise get wrong.

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?

Opens with the action, then two short paragraphs of constraints, then the return. Every sentence carries information, though the return statement is marginally redundant given an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the invariant, id/order preservation, and time behavior, and an output schema exists so return-value detail isn't needed in prose. What's missing is the auth/ownership expectation for edit_token (e.g. token invalidation on rotation), which sibling tools like rotate_edit_token imply is relevant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (block_id, edit_token) are already documented in the schema. The description adds no extra meaning to either beyond what the schema provides; baseline 3 applies.

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?

Names a specific verb and resource (removes one block from an agenda) and the scope is narrowed further than the bare name would suggest. An agent can distinguish it from update_block and reorder_blocks without opening either schema.

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

Usage Guidelines4/5

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

States a clear precondition ('an agenda must keep at least one block, so this fails on the last one') which is decision-relevant, and implicitly routes structural changes to siblings. It doesn't explicitly name an alternative tool for reordering or resizing, but the constraints define usage well enough.

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