Skip to main content
Glama

TT Uni Video Status

tt_uni_video_status
Read-onlyIdempotent

Processing status (processing / ready ...) and duration of a lesson's video, refreshed from VdoCipher.

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

Input Schema

NameRequiredDescriptionDefault
lesson_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the value is 'refreshed from VdoCipher', implying a live remote fetch on each call, plus the AUTH-REQUIRED note and teacher-only authorization gate. It does not describe latency or failure behavior when a video has not yet been uploaded, which keeps it short of 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 opening sentence is front-loaded and efficient and the auth note is well placed. The remaining bulk is shared TT Uni boilerplate about teaching rules, INR pricing, GST and the 50% revenue split, none of which bears on reading a video's processing status and which competes for attention with 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?

With no output schema, the description does the right thing by naming the returned fields and giving example status values, and it establishes the authorization gate. What is missing is the full status enumeration and what happens for a lesson that has no uploaded video yet, so an agent could still be surprised by a returned state.

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

Parameters3/5

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

There is one parameter, lesson_id, with 0% schema description coverage, so the description carries the burden. 'A lesson's video' implies lesson_id identifies the lesson, but it gives no guidance on where to obtain the id (e.g., from tt_uni_list_my_courses or tt_uni_save_lesson) or its format, so it only partially compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names the resource (a lesson's video) and the exact return values (processing status with example values 'processing / ready' and duration), which is more specific than a title restatement. It does not name a sibling such as tt_uni_set_lesson_video to contrast with, but the read-oriented purpose is unambiguous.

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

Usage Guidelines3/5

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

The description states eligibility (approved TT Uni teachers only, others redirected to the teach URL) and an auth requirement, which frames who can call it. However, it never says when to call this versus re-uploading via tt_uni_set_lesson_video or polling cadence after an upload, so the actual usage trigger is only implied.

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