Skip to main content
Glama

secondbrain

by media.secondbrain
OverviewDiscussionsAdmin

get_meetings

Read-only

Lista los RECAPS del workspace: las reuniones grabadas.

Un recap es una reunión que se grabó y procesó: queda el audio, la
transcripción, un resumen por tramos y los ACCIONABLES que la IA sacó. No
es una entrada de calendario (eso es get_events) ni una nota escrita a mano.

Esta lista no trae la transcripción, que es larga: pedí una puntual con
get_meeting, y sus accionables con get_meeting_actionables.

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada
meeting_type_idNo
meeting_group_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, and closed-world safety. The description adds useful behavioral scope beyond annotations: this list excludes the long transcription, and a recap includes audio, transcript, summaries, and AI-extracted actionables. It does not cover auth, rate limits, or pagination, but those are secondary here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight paragraphs: purpose first, then a definition of recap, then routing to detail tools. Every sentence adds information with no repetition or filler.

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

Completeness3/5

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

Complete enough to select the tool, but incomplete for invocation because two parameters (meeting_type_id, meeting_group_id) remain undocumented in both schema and description. With no output schema and 50% schema coverage, the description could have done more to explain the filter parameters and list behavior.

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

Parameters2/5

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

Schema description coverage is 50%: limit and workspace_id are documented, but meeting_type_id and meeting_group_id have no descriptions anywhere. The tool description only implies workspace scoping and adds no meaning for the undocumented filters, failing to compensate for the coverage gap.

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 (Lista) and resource (RECAPS del workspace: las reuniones grabadas), and defines what a recap is. It explicitly distinguishes this tool from get_events (calendar entries) and handwritten notes, so an agent can route correctly without opening sibling 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?

Explicitly says when not to use this tool (not calendar entries, not notes) and names the alternatives for deeper detail: get_meeting for a single recap and get_meeting_actionables for action items. The guidance is clear and actionable.

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

All secondbrain toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources