Skip to main content
Glama

TT Uni Session Recording

tt_uni_session_recording
Destructive

Manage a live session's recording PARTS (a session can have several, played in order). Every action WRITES: add and update change the parts, remove deletes one, unlock hands the session back to the automatic Zoom pick. action = - add: session_id + exactly one of url (an https link to the recording: a Zoom share or download link, Google Drive, S3 or any direct video link; VdoCipher imports it) or video_id (a VdoCipher id the teacher uploaded). Adds a part at the END. - update: recording_id + visible (true/false: hide a part from learners without deleting it) and/or position (1-based order). - remove: recording_id. Deletes that part; not recoverable here, so confirm with the teacher first. - unlock: session_id. Hands the parts back to the automatic Zoom pick and re-runs it now, which may replace the parts. Any add/update/remove LOCKS the session (recordings_locked), so the automatic Zoom pick stops changing its parts. Part ids, statuses and lengths are in tt_uni_get_course (sessions -> recordings); a URL part goes importing -> processing -> ready, and learners can play a part only when it is ready and visible. Length always comes from VdoCipher. Returns the session's cohort with every session's parts.

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": {
      "action": "<action>"
    },
    "name": "tt_uni_session_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoadd: https link to the recording (Zoom, Drive, S3, direct)
actionYesadd | update | remove | unlock
visibleNoupdate: show (true) or hide (false) the part
positionNoupdate: new 1-based position
video_idNoadd: a VdoCipher id the teacher uploaded
session_idNofor add / unlock
recording_idNothe part's id, for update / remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true) it discloses that every action writes, that add/update/remove set recordings_locked and stop the automatic Zoom pick, that remove is not recoverable here, that unlock re-runs the pick and may replace parts, and the importing -> processing -> ready lifecycle gating playability. These are substantive traits annotations cannot express; only the response payload description is thin.

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

Conciseness3/5

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

The action list is front-loaded and cleanly bulleted, but it is followed by a large block of generic marketplace boilerplate (tips rules, promised returns, 30-day market data, INR pricing with 18% GST, 50% revenue share) that is only marginally relevant to mutating recording parts and dilutes the operative 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?

For a 7-parameter mutation tool with no output schema, the definition covers auth requirement, write semantics, locking side effects, deletability, and the return shape (the session's cohort with every session's parts). Only the returned payload's structure and failure modes are left lightly specified.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real constraints absent from the schema: exactly one of url or video_id on add, which URL sources VdoCipher accepts, that video_id must be an id the teacher uploaded, and that position is 1-based order while visible hides a part from learners without deleting it.

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?

States a specific verb set and resource: manage a live session's recording PARTS, with the four actions (add/update/remove/unlock) enumerated and their distinct effects. It also names the read-side sibling (tt_uni_get_course) where part ids, statuses and lengths live, so an agent can separate it from the query tool without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit per-action selection rules (add requires session_id plus exactly one of url/video_id; update takes recording_id with visible and/or position; remove takes recording_id; unlock takes session_id) and an exclusion-style caution to confirm with the teacher before remove. It also names the precondition (approved TT Uni teachers only) plus a redirect URL for everyone else.

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