Skip to main content
Glama

Coline

Summarize meeting

summarize_meeting
Idempotent

Writes or refreshes a meeting's summary, decisions and action items from its notes and transcript.

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": {
      "workspace": "<workspace>",
      "eventId": "<eventId>"
    },
    "name": "summarize_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoWrite it again even if nothing changed.
eventIdYesEvent id from list_events.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
sourceKindNomanual_regen

Output Schema

NameRequiredDescriptionDefault
intelligenceYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the mutation and repeat-safety profile is covered structurally. The description adds that output includes summary, decisions and action items derived from notes/transcript, but it never says whether an existing (possibly hand-edited) summary is overwritten, nor what permissions or transcript states are required. With annotations doing the safety work, a 3 is appropriate.

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?

A single dense sentence with no filler, leading with the action and following immediately with the produced artifacts and their source. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be explained, and the description adequately conveys what the tool produces and from what inputs. It falls just short on overwrite semantics and any dependency on prior notes capture, which matter for a write tool with a 'refresh' mode.

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 75%, so most parameters are already documented — force ('Write it again even if nothing changed'), eventId, and workspace all carry descriptions. The gap is sourceKind, whose four enum values are undescribed; the description's 'from its notes and transcript' only loosely gestures at the notes/transcript/hybrid distinction and adds no guidance on when to pick each mode.

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?

Uses a specific verb pair ('Writes or refreshes') with a named resource ('meeting's summary, decisions and action items') and states the input source ('from its notes and transcript'). An agent can distinguish this write operation from read-only siblings like get_meeting_summary, though the description never names extract_meeting_action_items even though the overlap in 'action items' makes that the most confusable neighbor.

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

Usage Guidelines3/5

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

Usage is only implied — the phrase 'writes or refreshes' suggests calling it to generate a new summary or regenerate a stale one, and the force parameter hints at re-running. There is no explicit statement of when to use this versus get_meeting_summary or extract_meeting_action_items, and no prerequisites such as requiring notes or a transcript to exist first.

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