Skip to main content
Glama

get_meetings

Read-onlyIdempotent

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_meetings"
  }
}

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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond that: the result set excludes transcripts (which are long) and points to the tools that retrieve them, which shapes how an agent should follow up. It stops short of describing return fields or pagination behavior beyond the limit param.

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?

Short paragraphs, front-loaded with the core definition, then the negative contrast, then the follow-up routing. Every sentence carries information an agent needs; no filler.

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?

With no output schema, the description correctly explains what a recap consists of and what the list omits, which is the most important missing context. Minor gaps remain: the two undocumented filter params and any indication of result fields or ordering.

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?

The description says nothing about any of the four parameters. Schema coverage is only 50%: limit and workspace_id are documented in the schema (including the useful 'omit = ALL workspaces' semantics), but meeting_type_id and meeting_group_id carry no description in either place. The description does not compensate for that 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 and resource ('Lista los RECAPS del workspace') and then defines the concept precisely: a recorded and processed meeting with audio, transcript, per-segment summary and AI-extracted actionables. It explicitly contrasts with get_events (calendar) and handwritten notes, so an agent can distinguish it from siblings without opening any 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 explicit routing: use get_meeting for a single meeting's transcript and get_meeting_actionables for its actionables, since this list deliberately omits the transcript. It also names get_events as the alternative for calendar entries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources