Skip to main content
Glama

TT Uni Save Cohort

tt_uni_save_cohort
Destructive

Add or edit a cohort (a dated live batch of a LIVE-kind course). WRITES: creates one, or overwrites the fields you pass on an existing one. New: course_id + fields{starts_on "YYYY-MM-DD", ends_on?, price_inr?, status? draft|coming_soon|open|closed, community_link?, access_days?, enrol_closes_at? "YYYY-MM-DD HH:MM" IST (null = open until it starts), seats? (null = no limit; sold out closes enrolment), record_sessions? (false = live only, no recording), name? (e.g. "Nov 2026 batch"), join_url? (one meeting link for every session; a session's own link wins), alt_hosts? [Tradetron emails who may also start the batch meeting], materials? [{label, url}] (enrolled learners only)} + optional sessions[{starts_at "YYYY-MM-DD HH:MM" IST, duration_minutes, topic, join_url?}]. Edit: cohort_id + fields to change (no sessions — use tt_uni_save_session). Same rules as Studio's cohort form. 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_cohort"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
sessionsNo
cohort_idNo
course_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description earns credit by explaining the actual overwrite semantics ("overwrites the fields you pass on an existing one") rather than full replacement, plus draft-only publication, GST/50% revenue split, and the exact Zoom recording matching window. It does not say what happens on a failed/partial write, which is the remaining behavioral gap for a destructive tool.

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

Conciseness4/5

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

Front-loaded with purpose and a WRITES: marker, then a second block for auth/marketplace rules; the optionality markers (?) make the field list scannable. It is dense and long, and the teaching-rules/GST paragraph is the portion least needed to invoke the tool correctly, keeping it just shy of a 5.

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 4-param destructive mutation with no output schema and no annotation detail, this is nearly complete: field semantics, recording matching, and access rules are all covered. The one omission is the return value (presumably the cohort_id), which the agent needs to chain into tt_uni_save_session.

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 both fields/sessions are free-form objects, so the description must carry the load — and it does, enumerating starts_on, ends_on, price_inr, status enum values, enrol_closes_at with IST and null semantics, seats null behavior, record_sessions, join_url precedence, alt_hosts, materials, and the sessions[] shape. Null conventions and per-field meaning go well beyond anything the bare schema provides.

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 pair and resource ("Add or edit a cohort") and immediately defines the domain object: "a dated live batch of a LIVE-kind course." It also distinguishes create vs. edit paths and names the sibling boundary mid-sentence ("no sessions — use tt_uni_save_session"), so an agent can select it 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?

Explicit routing: new cohorts need course_id + fields, edits need cohort_id + fields to change, and sessions/recordings are redirected to tt_uni_save_session and tt_uni_session_recording. It also states gating conditions up front — approved TT Uni teachers only, drafts only, AUTH-REQUIRED — which tells the agent when not to call it.

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