Skip to main content
Glama
Sign In
Fathom-Simple-MCP

Fathom-Simple-MCP

by druellan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_meeting_details

Read-only

Retrieve meeting summary and metadata using the recording identifier.

Instructions

Retrieve comprehensive meeting details including summary and metadata (without transcript).

Example: get_meeting_details([recording_id])

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

Input Schema

NameRequiredDescriptionDefault
recording_idYesThe recording identifier

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds useful context: returns summary, metadata, and explicitly states (without transcript). No contradictions.

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 sentences plus example. Front-loaded with purpose. No redundant information. Highly efficient.

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?

With output schema existing, description adequately covers what the tool returns (summary, metadata, no transcript) and example. No gaps for a simple single-parameter read tool.

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%. Description adds an example call showing the parameter but does not provide additional meaning beyond what the schema describes.

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?

Clearly states it retrieves comprehensive meeting details including summary and metadata, explicitly excluding transcript. Differentiates from get_meeting_transcript which would provide transcript. Includes example call.

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

Usage Guidelines4/5

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

Implicitly guides when to use: when summary/metadata needed, not transcript. Lacks explicit 'when not to use' or direct sibling comparison, but the exclusion of transcript is clear enough.

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