Skip to main content
Glama

TT Uni Create Course

tt_uni_create_course

Create a NEW draft course from markdown in the TT Uni format (tt_uni_course_format). Show the teacher the full outline and price and get a yes before calling. Returns the draft course with its id. A lesson's video: line takes a public https link to a video file or the teacher's own VdoCipher id; lessons can also get videos later. A LIVE course gets its chapters too: each chapter is one session's plan and its lessons are the topics, with their notes (no tests on a live course). A field over its limit (title 160, summary 255, prerequisites 255, outcome 200, chapter/lesson title 160 characters) is refused with the count and the limit; nothing is cut short. Replies with a compact summary (ids, titles, status); response="full" returns everything.

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": {
      "markdown": "<markdown>"
    },
    "name": "tt_uni_create_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
markdownYes
responseNosummary (default: ids, titles, status) | fullsummary

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 that nothing is published without review team approval, that over-limit fields are refused with a count and limit rather than truncated, and that the tool returns the draft with its id. It also adds operating constraints (INR pricing excluding 18% GST, 50% teacher share, content rules) that the annotation set does not convey at all.

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 the action and its confirmation step, then returns, then structural rules, then marketplace/policy context. It is dense and long, but nearly every sentence answers a question the agent would otherwise have to guess at; the policy block is the only portion that could be trimmed for a single-call context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even with no output schema, the definition explains the return shape (draft course plus id, compact summary vs response="full"), validation failure behavior, and auth requirements. For a two-parameter creation tool this leaves little an agent needs to infer.

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?

The markdown parameter has no schema description, so the description carries the burden: it explains the video: line syntax (https link or VdoCipher id), that live courses use chapters as sessions and lessons as topics, that live courses have no tests, and lists per-field character limits. The response parameter is already documented in the schema, so nothing is missing.

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 with scope qualifiers — 'Create a NEW draft course from markdown in the TT Uni format' — which separates it from tt_uni_update_course (existing courses) and tt_uni_course_format (format reference). The parenthetical naming of the format tool makes the boundary explicit.

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?

Gives a concrete pre-call workflow ('Show the teacher the full outline and price and get a yes before calling') and a hard eligibility gate (approved TT Uni teachers only, with a fallback URL). It also implies follow-up tools ('lessons can also get videos later'), but never explicitly routes editing of an existing course to a sibling.

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