Skip to main content
Glama

Meeting AI notes

get_summary

AI notes and copilot moments of a meeting. Paged.

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": {
      "id": "<id>"
    },
    "name": "get_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNoFrom the previous page footer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. 'Paged' does disclose that results come in pages, which is genuine behavioral information, but nothing is said about permissions, ordering, whether copilot moments can be empty, or what a page contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments with zero waste and the core subject front-loaded, but the terseness crosses into under-specification rather than serving clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read tool with an undocumented required id, an undescribed return payload, and no output schema needs more than this. The agent cannot tell what fields come back or how notes differ from copilot moments.

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?

Schema coverage is 50%: offset is described in the schema ('From the previous page footer'), while id is documented only by type and length. The description's 'Paged' loosely corroborates offset but adds no meaning for id or for how pagination terminates.

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

Purpose3/5

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

The fragments 'AI notes and copilot moments of a meeting' identify the resource but leave the verb implicit (it is a retrieval, inferred from the name and parameters). It is not clearly differentiated from the sibling get_note, which plausibly returns notes of a meeting too.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over get_note, get_transcript, or get_brief. The only hint is 'Paged,' which says nothing about call conditions or alternatives.

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.