Skip to main content
Glama
ChatterBoxIO

ChatterBox MCP Server

by ChatterBoxIO

summarizeMeeting

Generate concise meeting summaries from transcripts to capture key decisions and action items.

Instructions

Generate a concise summary of a meeting's contents from its transcript

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transcriptYesThe meeting transcript to summarize

Implementation Reference

  • The handler function for the 'summarizeMeeting' tool. It takes a meeting transcript as input and returns a structured text prompt with instructions for identifying main topics and summarizing them, embedding the provided transcript.
      async ({ transcript }: { transcript: string }) => {
        return {
          content: [{
            type: "text",
            text: `Given an online call transcript formatted as:
    Speaker: Transcript
    
    Identify main topics of the conversation, summarize them in the following format:
    - Topic Title
    Topic summary
    
    Remove smalltalk and insignificant topics. Do not include any introductory wording.
    
    Transcript:
    ${transcript}`
          }]
        };
      }
  • Zod input schema defining the 'transcript' parameter for the 'summarizeMeeting' tool.
    {
      transcript: z.string().describe("The meeting transcript to summarize"),
    },
  • src/index.ts:170-194 (registration)
    Registration of the 'summarizeMeeting' tool using McpServer.tool(), including name, description, input schema, and handler function.
    server.tool(
      "summarizeMeeting",
      "Generate a concise summary of a meeting's contents from its transcript",
      {
        transcript: z.string().describe("The meeting transcript to summarize"),
      },
      async ({ transcript }: { transcript: string }) => {
        return {
          content: [{
            type: "text",
            text: `Given an online call transcript formatted as:
    Speaker: Transcript
    
    Identify main topics of the conversation, summarize them in the following format:
    - Topic Title
    Topic summary
    
    Remove smalltalk and insignificant topics. Do not include any introductory wording.
    
    Transcript:
    ${transcript}`
          }]
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool generates a summary but doesn't describe key behaviors like output format, length, quality, or any limitations (e.g., handling long transcripts, language support). For a tool with no annotations, this leaves significant gaps in understanding how it operates.

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?

The description is a single, efficient sentence that clearly states the tool's purpose without any wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence earns its place by conveying essential information.

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?

Given the tool's moderate complexity (summarization task) and lack of annotations and output schema, the description is minimally adequate. It covers the basic purpose but misses behavioral details and usage context. Without an output schema, it should ideally explain return values, but it doesn't, leaving gaps in completeness for effective agent use.

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?

The schema description coverage is 100%, with the single parameter 'transcript' well-documented in the schema. The description adds no additional parameter details beyond what the schema provides (e.g., format expectations, length constraints). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 clearly states the tool's purpose: 'Generate a concise summary of a meeting's contents from its transcript.' It specifies the verb ('generate'), resource ('summary'), and source ('transcript'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like getMeetingInfo or joinMeeting, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools (getMeetingInfo, joinMeeting) or any context for choosing this tool over others. The usage is implied from the purpose, but there are no explicit when/when-not instructions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChatterBoxIO/chatterboxio-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server