Skip to main content
Glama
Sign In
fathom-mcp-server

fathom-mcp-server

by luminarylane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fathom_get_summary

Retrieve AI-generated summary for a past meeting. Provide the meeting recording ID to receive markdown-formatted content.

Instructions

Get the AI-generated summary for a specific meeting. Returns markdown-formatted summary.

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": {
      "recording_id": "<recording_id>"
    },
    "name": "fathom_get_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
recording_idYesThe meeting/recording ID from fathom_list_meetings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions 'returns markdown-formatted summary' which hints at read-only behavior, but does not state side effects, auth requirements, or rate limits. Adequate but could be more explicit.

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?

Two short, direct sentences with no redundant information. Front-loaded with purpose and output format.

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

Completeness5/5

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

For a simple retrieval tool with one required parameter and no output schema, the description is complete: it specifies input source, output format, and core functionality.

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% for the single parameter, which already explains it comes from fathom_list_meetings. The tool description adds no additional semantic information beyond what the schema provides.

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

Purpose5/5

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

Description clearly states the tool gets an AI-generated summary for a specific meeting, explicitly mentioning the markdown format. It is distinct from siblings like fathom_get_transcript (different output) and fathom_list_meetings (different purpose).

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?

No explicit guidance on when to use this tool vs alternatives. It is implied that one uses it when needing a summary rather than a transcript, but there are no when-not or alternative recommendations.

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

Deploy Server

Other Tools