Skip to main content
Glama

TT Uni Get Course

tt_uni_get_course
Read-onlyIdempotent

Read one of the teacher's courses in full: fields, chapters -> lessons (id, title, notes, preview, video status/duration), cohorts -> sessions, and markdown — the whole course with id: lines. To make structural edits, change that markdown and send it back with tt_uni_update_course; the id lines keep existing lessons matched. Live courses: each cohort has zoom (null or meeting_id, join_url, passcode_set, host, alt_hosts, closed_at). The meeting passcode is never returned (it is a credential); the passcode and the full join link are on the course's Studio page. Each session has its recording in PARTS: recordings [{id, position, visible, source (zoom|upload|url|vdocipher_id), status (found | uploading | downloading | importing | processing | ready | failed), error, duration_seconds (from VdoCipher), video_id, zoom_start_at}], plus recording_status (null | processing | ready | failed), has_recording (true only when a visible part is ready, so learners can play it) and recordings_locked (true after any manual change: the automatic Zoom pick then leaves the parts alone). Change parts with tt_uni_session_recording. Recordings arrive by themselves only from Zoom meetings on Tradetron's Zoom account with cloud recording on: the batch meeting TT Uni books, a session's own booked meeting, or a pasted link to a meeting on that account. A recording is matched by the meeting number in the link (zoom.us/j/) and by time: it must start between 60 minutes before the session and 180 minutes after its scheduled end. A pasted link to a meeting on any other Zoom account is never picked up: add that recording with tt_uni_session_recording (action=add, a link). With record_sessions false nothing is recorded or offered. Text comes back exactly as the teacher typed it; the markdown quotes a value only when it has to, so sending it back unchanged changes nothing.

TT Uni is Tradetron's course marketplace (tradetron.tech/learn). These tools act as the signed-in user and work only for approved TT Uni teachers; anyone else is pointed to https://tradetron.tech/learn/teach. DRAFTS ONLY: nothing is published until the TT Uni review team approves the course. TT Uni teaching rules: no tips or buy/sell calls; no promised returns and no P&L screenshots as proof; any market data shown must be at least 30 days old; disclose any paid strategy of your own that the course mentions. Prices are in INR and exclude GST (18% is added at checkout); the teacher earns 50% of the price. AUTH-REQUIRED.

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": {
      "course_id": "<course_id>"
    },
    "name": "tt_uni_get_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, but the description adds substantial context beyond them: passcodes are never returned, recording matching follows meeting number and time-window rules, recordings_locked means automatic Zoom picking stops, record_sessions=false disables recording, and text comes back exactly as typed. It also states AUTH-REQUIRED and that the tools work only for approved TT Uni teachers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core read purpose is front-loaded, but the description then runs on through extensive domain rules about the marketplace, teaching rules, GST, teacher earnings, and detailed recording mechanics. Much of that text does not help an agent invoke this one-parameter read and dilutes the actionable content.

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?

With no output schema, the description does a good job enumerating the nested return structure, including chapters, lessons, cohorts, sessions, recordings, recording_status, has_recording, and recordings_locked. It is less complete about the course-level 'fields' and the origin of course_id, but overall it is sufficient for a complex read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter is course_id, and schema description coverage is 0%. The description never explains what course_id is, where to get it, or whether it is the id returned by the teacher's course list; with low schema coverage it should compensate but does not.

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?

The description states a specific verb and resource: 'Read one of the teacher's courses in full', then enumerates the returned structure (fields, chapters -> lessons, cohorts -> sessions, and markdown). It also distinguishes this read from structural edits sent through tt_uni_update_course, so an agent can tell it apart from the sibling mutation tool.

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?

It explicitly routes structural edits to tt_uni_update_course and recording changes to tt_uni_session_recording, giving clear alternatives for adjacent operations. It does not explicitly say how to obtain course_id (for example via tt_uni_list_my_courses) or state when not to use this tool, so it falls short of a full 5.

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.

Resources