Skip to main content
Glama

get_collaboration_transcript

Read-onlyIdempotent

Retrieve the complete transcript of an ongoing collaboration by ID without ending the session, so you can review prior agent messages and continue the discussion.

Instructions

Get the full transcript of a collaboration without ending it.

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": {
      "collaboration_id": "<collaboration_id>"
    },
    "name": "get_collaboration_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
collaboration_idYesThe collaboration ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description still adds a non-obvious guarantee beyond them: retrieving the transcript leaves the collaboration running. It says nothing about transcript length, truncation, or formatting, which keeps it short of a 5.

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?

A single twelve-word sentence with the action front-loaded and the key constraint ('without ending it') placed for emphasis. No filler.

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

Completeness4/5

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

For a simple, annotation-rich, single-parameter read tool, this is nearly sufficient. The only real gap is that no output schema exists and the description says nothing about what a transcript contains or how large it may be.

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% for the single required parameter, collaboration_id, so the schema already carries the parameter meaning. The description adds nothing about the ID's format or provenance, which is acceptable but not additive.

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?

States a specific verb and resource: 'Get the full transcript of a collaboration.' The trailing clause 'without ending it' implicitly separates it from lifecycle-ending siblings such as end_collaboration, though no sibling is named explicitly.

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 phrase 'without ending it' implies the use case (inspect an ongoing collaboration while keeping it alive) but never states when to prefer this over end_collaboration or how it relates to list_collaborations. Usage is inferable rather than explicit.

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