Skip to main content
Glama

Coline

Find action items in meeting notes

extract_meeting_action_items

Reads a meeting's notes and pulls out its action items, adding them to the notes as a checklist.

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": "extract_meeting_action_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent id from list_events.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
itemsYes
extractedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent operation, and the description usefully clarifies what the mutation actually is: a checklist appended to the notes. It does not say whether existing checklists are replaced or duplicated on repeat calls, which matters given idempotentHint=false, nor does it mention any permission requirements.

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 sentence that front-loads the read behavior and ends on the side effect, with no filler. Every clause carries meaning.

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?

With an output schema present, return values need no explanation, and the core effect on the notes is stated. Still, for a mutating tool that is explicitly non-idempotent, the description leaves open whether repeated calls duplicate the checklist, which is a material gap for correct invocation.

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%, with workspace and eventId fully documented in the schema itself, so the baseline applies. The description adds no information about parameter formats or constraints, but none is needed.

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 concrete verb phrase and resource: reads meeting notes, extracts action items, and writes them back as a checklist. The write-back detail distinguishes it from the read-only sibling list_meeting_action_items, though the description never names that sibling explicitly.

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?

The phrase 'adding them to the notes as a checklist' implies this is the mutating variant, so an agent can infer when to prefer it over a plain listing. However, there is no explicit when-to-use/when-not guidance and no mention of the alternative tool by name, leaving selection 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