Skip to main content
Glama

TT Uni Set Lesson Video

tt_uni_set_lesson_video
DestructiveIdempotent

Attach a video to a lesson, replacing any current one. Pass exactly one of url (public https link to the video file; VdoCipher fetches it, status starts as processing) or video_id (a VdoCipher id the teacher uploaded). Check progress with tt_uni_video_status. File uploads from chat are not supported: host the file or upload it in the Studio.

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": {
      "lesson_id": "<lesson_id>"
    },
    "name": "tt_uni_set_lesson_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
video_idNo
lesson_idYes

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?

Annotations already declare destructiveHint=true and idempotentHint=true, and the description corroborates the destructive part by saying any current video is replaced. It adds behavior beyond the annotations by disclosing the async processing state ("status starts as processing") and the auth/approval requirement. It does not say what happens to the previously attached video asset or how failure of the fetch is surfaced, which keeps it below a 5.

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 first paragraph is tightly front-loaded and every sentence is operational. The second paragraph, however, is largely generic marketplace boilerplate (INR pricing, GST, 50% revenue share, content rules about market data age and P&L screenshots) that has no bearing on attaching a video to a lesson, which 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?

For a three-parameter mutation tool with no output schema and existing annotations, the definition covers the important ground: the two input modes, the replace behavior, the async status contract, and the authorization gate. Missing pieces are minor, such as what a failed VdoCipher fetch leaves the lesson in.

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 description coverage is 0%, so the description carries the full burden: it defines `url` as a public https link that VdoCipher fetches and `video_id` as a VdoCipher id uploaded by the teacher, and it expresses the one-of constraint that the JSON schema cannot encode. `lesson_id` is the only required parameter and goes unexplained, though its meaning is self-evident from the tool name.

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 opening sentence gives a precise verb and resource: "Attach a video to a lesson, replacing any current one." It also declares the replacement semantics up front, so the agent knows this is a mutating set operation rather than an append, and it is clearly distinct from sibling tools such as tt_uni_course_media or tt_uni_video_status.

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?

It states the exclusive-or rule explicitly ("Pass exactly one of `url` ... or `video_id`"), explains what each mode is for, and routes follow-up work to tt_uni_video_status. It also names a genuine exclusion (chat file uploads are unsupported; host the file or use the Studio) and the authorization precondition that only approved TT Uni teachers can 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