Skip to main content
Glama

Read a meeting summary

get_meeting
Read-onlyIdempotent

Retrieve a full meeting summary with decisions, tasks and their status, open questions, participants, speaking time, call link, and notes. Use it to find action items or follow-up details.

Instructions

The full summary of a meeting: the short version, decisions, tasks (marked done or not), open questions, participants and how much each of them spoke, the call link, and the notes the user wrote for the meeting. For "What are my action items from the Northwind call?", "Write a follow-up email after today's sync", "Which tasks from Monday are still open?" Read-only.

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": "<meeting>"
    },
    "name": "get_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
meetingYesMeeting id from search or list_meetings

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the trailing 'Read-only.' sentence is pure restatement and earns nothing. The content enumeration does add real behavioral context about what the agent will receive (talk-time stats, done flags), but with an output schema present that value is partly duplicated. No information on failure behavior when a meeting id is invalid or inaccessible.

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 return content, then example intents, then the read-only flag. Every clause carries information, though the enumeration is long and the final 'Read-only.' sentence is redundant with annotations and could be dropped.

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?

A one-required-parameter read tool with full schema descriptions, a complete annotation set, and an output schema needs only to say what it returns and when to reach for it — both of which are covered. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100% and the single 'meeting' parameter already documents its provenance ('Meeting id from search or list_meetings'). The description adds no format, validation, or id-provenance detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and enumerates its payload precisely: short summary, decisions, tasks with done state, open questions, participant talk-time, call link, and user notes. That is far more informative than the title alone. It does not, however, distinguish itself from the sibling get_transcript, which an agent might reasonably consider for the same requests.

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?

Three concrete user-utterance examples (action items from a named call, drafting a follow-up email, finding open tasks from a given day) give clear positive usage context and implicitly define scope. There is no explicit exclusion such as 'use get_transcript for raw dialogue' or 'use list_meetings to discover ids', so the agent must infer the boundary.

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

Deploy Server

Other Tools