Skip to main content
Glama

TT Uni Submit For Review

tt_uni_submit_for_review
Idempotent

Send a finished draft course to the TT Uni review team. This does NOT publish it: it goes live only if they approve. Returns status in_review, or the list of what to fix first (e.g. lessons without a ready video). Before calling, check the course against the teaching rules with the teacher and get their go-ahead.

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": {
      "course_id": "<course_id>"
    },
    "name": "tt_uni_submit_for_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already say readOnlyHint=false, idempotentHint=true, destructiveHint=false, but the description adds substantial context beyond them: the call does not publish, publication only follows review-team approval, the response is either status in_review or a list of blockers (e.g. lessons without a ready video), and authentication as an approved TT Uni teacher is required. This is exactly the kind of state-transition and failure-mode detail annotations cannot carry.

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 paragraph is well front-loaded and wastes nothing. The second block, however, repeats the draft-only message already stated ('DRAFTS ONLY: nothing is published until the TT Uni review team approves') and carries tangential marketplace material such as INR pricing, 18% GST, and the 50% revenue split that does not affect how this call is made.

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 correctly explains both return shapes (in_review status or a fix-it list). Auth requirements and the compliance preconditions are all present. Only the identity/semantics of course_id is left implicit, which is a minor gap for a one-parameter tool.

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?

Schema description coverage is 0% for a single required integer course_id, so the description carries the burden. 'A finished draft course' implies the id must reference a completed draft and not a published or half-built course, but the parameter itself is never named or explained, leaving the agent to infer that course_id is that draft.

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 ('Send a finished draft course to the TT Uni review team') and immediately bounds the scope ('This does NOT publish it'). The pre-submission/approval workflow is distinguishable from sibling mutation tools like tt_uni_update_course or tt_uni_delete without opening any 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?

Gives an explicit precondition: the course must be a finished draft, and the teacher must have been walked through the teaching rules and given go-ahead before calling. It does not name a sibling to use instead (e.g. for checking readiness or status), so it stops short of full routing guidance.

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