Skip to main content
Glama

TT Uni Save Lesson

tt_uni_save_lesson
Destructive

Add or edit a lesson (WRITES: creates one, or overwrites the fields you pass on an existing one). New lesson: chapter_id + title (+ notes, preview, video_url or video_id). Edit: lesson_id + only what changes: title, notes (markdown shown under the video), preview (true = free preview lesson), position, move_to_chapter_id, video_url / video_id. video_url must be a public https link to a video FILE (it is fetched and transcoded); video_id is a VdoCipher id the teacher uploaded. If it answers TTUNI_WRITE_UNCONFIRMED the lesson may exist already: read the course back before adding it again.

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_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
titleNo
previewNo
positionNo
video_idNo
lesson_idNo
video_urlNo
chapter_idNo
move_to_chapter_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the partial-overwrite semantics ('overwrites the fields you pass'), that drafts are not published until review, that video_url is fetched and transcoded, the required auth, and a specific error code with retry guidance. This is exactly the context an agent needs to avoid duplicating a lesson, and it is consistent with destructiveHint=true and idempotentHint=false.

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?

The operation and its two modes are front-loaded in the first paragraph, which is the part an agent needs first. The trailing marketplace paragraph is well organized but includes pricing/tax/revenue-share details (INR, 18% GST, 50% earnings) that do not affect how this tool is invoked.

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 9-parameter mutation tool with no output schema, the description covers write semantics, auth, draft-only status, media handling and the duplicate-risk error path. It does not say what the call returns (e.g., the created lesson_id) or how position is interpreted when omitted, which the missing output schema would otherwise need to cover.

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 description coverage is 0% across 9 parameters, so the description must carry the whole burden and it largely does: notes is 'markdown shown under the video', preview means 'free preview lesson', position and move_to_chapter_id are described in edit context, video_url must be a public https link to a video FILE, and video_id is a VdoCipher id. Only chapter_id/lesson_id semantics are left to the names themselves.

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 opens with a precise verb+resource: 'Add or edit a lesson', and immediately clarifies it is a write that either creates a record or overwrites 'the fields you pass on an existing one'. It then enumerates the two operating modes with their respective required inputs, so an agent can distinguish create vs. edit 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 Guidelines4/5

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

It gives explicit conditions: 'New lesson: chapter_id + title' versus 'Edit: lesson_id + only what changes', plus a concrete recovery path when the tool answers TTUNI_WRITE_UNCONFIRMED ('read the course back before adding it again'). It also gates usage to approved TT Uni teachers with a pointer URL for others. The only gap is that it never names the sibling tt_uni_set_lesson_video as the alternative for swapping a video.

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