Skip to main content
Glama

get_meeting

Read-onlyIdempotent

Un recap entero: la transcripción completa y el resumen.

El resumen está armado sobre un mapa por tramos de la reunión, no sobre la
transcripción cruda de una sola pasada: por eso sigue el hilo de lo que se
fue diciendo. No incluye los accionables de la reunión: son una lista viva
que se confirma o se descarta, y tienen su propia tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "meeting_id": "<meeting_id>"
    },
    "name": "get_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
meeting_idYesID de la reunión
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

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description adds real content value: it explains the summary is built from a segmented map rather than a single pass over the raw transcript, which tells the agent why the summary tracks the thread of the discussion. It does not warn about transcript size or any truncation, which matters for a full-transcript read.

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?

Front-loaded with the payload ('Un recap entero: la transcripción completa y el resumen'), then two short sentences that each add a distinct fact: how the summary is derived and what is deliberately missing. 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 a simple two-parameter read tool, no output schema, and full annotation coverage, the description covers what comes back and what does not. The only real gap is the absence of any note on response size or handling of very long transcripts.

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%, with meeting_id and workspace_id both documented, including the useful default that omitting workspace_id searches all of the person's workspaces. The description adds nothing about either parameter, so the 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?

Opens with a specific statement of what is returned: the full transcript plus the summary for a meeting. It also distinguishes itself from get_meeting_actionables by stating actionables are explicitly excluded and live in their own tool, so an agent can route 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?

Gives a clear exclusion ('No incluye los accionables') and names the reason and the alternative tool that owns them. It stops short of an explicit positive trigger such as 'use this when the user asks for what was discussed in a meeting', leaving that to inference.

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