Skip to main content
Glama

Meeting transcript

get_transcript

Timestamped, speaker-attributed transcript 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_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNoFrom the previous page footer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: results are paginated and content is timestamped with speaker attribution. It omits what happens on a missing/invalid id, permission requirements, page size, and how end-of-results is signaled, which matters for a no-annotation read tool.

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 sentences with zero filler, front-loading the content shape and ending with the pagination constraint. Nothing repeated and nothing wasted.

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?

For a two-parameter read tool with no output schema and no annotations, the description should say more about the response envelope, since 'from the previous page footer' presumes a footer the agent has never seen described. It covers the content nature and pagination adequately but leaves return shape and termination behavior unstated.

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 50%: 'offset' is documented in the schema, but 'id' has no description. The description partially compensates by saying this is the transcript 'of a meeting', implying id identifies a meeting, and 'Paged' reinforces the offset's purpose. It does not add format, length, or validity details beyond that.

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 names a specific resource (a meeting transcript) and its shape (timestamped, speaker-attributed, paged), which distinguishes it from siblings like get_summary or get_note. It stops short of naming an explicit verb or contrasting directly with an alternative, so it is clear but not fully differentiated.

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 statement of when to fetch a transcript rather than get_summary, get_brief, or get_note, and no preconditions given. The only contextual hint is 'Paged', which implies repeated calls but not when to prefer this tool.

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.