Skip to main content
Glama

get_summary

Generate meeting summaries from recordings, providing clean markdown content without playback URLs for efficient review.

Instructions

Get summaries for one or more meeting recordings. Returns clean markdown with playback URLs stripped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recording_idsYesOne or more recording IDs (from list_meetings).

Implementation Reference

  • The handler function that executes the logic for the 'get_summary' tool, which involves fetching the summary from the client and formatting it with Markdown.
    async args => {
      const client = getClient();
    
      const fetchOne = async (rid: number): Promise<string> => {
        const cached = _summaryCache.get(rid);
        if (cached && Date.now() - cached.fetchedAt <= CACHE_TTL_MS) {
          return cached.text;
        }
        const result = await client.getSummary(rid);
        const summary = (result.summary ?? {}) as Record<string, unknown>;
        const md = summary.markdown_formatted as string | undefined;
        const text = md
          ? `# Summary (recording ${rid})\n\n${stripMdLinks(md)}`
          : `# Summary (recording ${rid})\n\nNo summary available.`;
        _summaryCache.set(rid, { text, fetchedAt: Date.now() });
        return text;
  • src/server.ts:442-453 (registration)
    Registration of the 'get_summary' tool in the MCP server.
    server.registerTool(
      'get_summary',
      {
        description:
          'Get summaries for one or more meeting recordings. Returns clean markdown with playback URLs stripped.',
        inputSchema: {
          recording_ids: z
            .array(z.number().int().positive())
            .min(1)
            .describe('One or more recording IDs (from list_meetings).'),
        },
      },
  • The underlying client method that performs the API request to retrieve the summary for a specific recording ID.
    async getSummary(recordingId: number): Promise<Record<string, unknown>> {
      return this._get(`/recordings/${recordingId}/summary`);
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns 'clean markdown with playback URLs stripped', which adds useful behavioral context about output formatting. However, it lacks details on permissions, rate limits, or error handling, leaving gaps for a tool with mutation implications (e.g., data processing).

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 two sentences, front-loaded with the core purpose and followed by output details. Every sentence adds value without waste, making it efficient and well-structured.

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 no annotations and no output schema, the description partially compensates by explaining the return format. However, for a tool that processes data (summaries), it lacks details on input validation, error cases, or what 'clean markdown' entails, leaving room for improvement in completeness.

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 description coverage is 100%, so the schema already documents the parameter fully. The description adds no additional meaning beyond what the schema provides (e.g., no extra syntax or format details). Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('Get summaries') and resource ('meeting recordings'), specifying it works for 'one or more' items. It distinguishes from siblings like 'get_transcript' by focusing on summaries rather than full transcripts, though it doesn't explicitly name alternatives. The purpose is specific but could be more differentiated.

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 description implies usage by mentioning 'recording IDs (from list_meetings)', suggesting list_meetings as a prerequisite, but it doesn't explicitly state when to use this tool versus alternatives like get_transcript or provide exclusions. Guidance is present but not comprehensive.

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/jerichosequitin/fathom-ai-mcp'

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