Skip to main content
Glama

TT Uni Save Session

tt_uni_save_session
Destructive

Add or edit a live session in a cohort (WRITES: creates one, or overwrites the fields you pass on an existing one). New: cohort_id + fields{starts_at "YYYY-MM-DD HH:MM" IST, duration_minutes, topic, join_url?, slides_url?}. Edit: session_id + fields to change. A session's recording is a list of PARTS: fields.recording_video_id (a VdoCipher id) on an edit ADDS that video as the last part and locks the parts against the automatic Zoom pick; it does not replace the others. The length always comes from VdoCipher; there is no length or duration field for a recording (duration_minutes is the session's scheduled length). To add a link, hide, reorder or remove parts, or hand them back to the Zoom pick, use 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.

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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tt_uni_save_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
cohort_idNo
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds materially beyond that: it says exactly what is overwritten ("overwrites the fields you pass"), that a recording_video_id edit appends as the last part and locks parts against the automatic Zoom pick, and that the length always comes from VdoCipher rather than duration_minutes. It also discloses the auth gate (approved TT Uni teachers) and that everything remains a draft until review.

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 tool-specific content is front-loaded and dense, but the description also carries a long marketplace boilerplate block (teaching rules, INR pricing, GST, 50% revenue share) that does not help an agent invoke this save-session tool. The Zoom recording-matching paragraph is relevant but could be tightened given it partly duplicates the handoff already stated for tt_uni_session_recording.

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 no-output-schema, three-parameter mutation tool this is unusually complete: modes, field formats, overwrite semantics, recording behavior, auth, and draft status are all covered. The one gap is what a successful call returns (e.g. the new session_id), which an agent would want in order to chain a follow-up recording edit.

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

Parameters5/5

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

Schema coverage is 0% and the fields parameter is an opaque anyOf object, so the description carries the full burden and does: it enumerates the field keys (starts_at, duration_minutes, topic, join_url?, slides_url?, recording_video_id), gives the time format and timezone ("YYYY-MM-DD HH:MM" IST), and clarifies that duration_minutes is scheduled length, not recording length. It also resolves the otherwise ambiguous requiredness by stating which parameters go with the create path versus the edit path.

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 and resource ("Add or edit a live session in a cohort") and immediately disambiguates the two modes by parameter shape (cohort_id+fields vs session_id+fields). It also names the sibling tt_uni_session_recording and the class of operations that belong there, so an agent can route without opening either 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?

Explicit when-to-use for both create and edit paths, plus explicit when-not-to-use with the named alternative ("To add a link, hide, reorder or remove parts... use tt_uni_session_recording"). It further explains when a recording arrives automatically versus when a manual add is required, including the condition that a link on another Zoom account is never auto-picked.

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