Skip to main content
Glama

TT Uni My Courses

tt_uni_list_my_courses
Read-onlyIdempotent

List the signed-in teacher's TT Uni courses: id, title, status (draft / in_review / live ...), kind, price_inr, lesson count, how many lessons have a ready video, public url and Studio url.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds material context the annotations cannot: authentication is required, the account must be an approved TT Uni teacher, and courses are drafts until the review team approves them. The remaining policy text (tips, P&L, price/GST, 50% split, 30-day data rule) is platform boilerplate with little bearing on invoking a read-only list call.

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 payload is front-loaded correctly: the first sentence says exactly what is listed and returned. But the bulk of the description is cumulative TT Uni policy (content rules, pricing, revenue split) that is repeated boilerplate for a read-only listing and dilutes the operative sentences.

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 carries the return-value burden and does so by naming the fields and the status enum. Authentication and eligibility are also covered. Missing only minor operational details such as ordering, pagination, and the result when the teacher has zero courses.

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 tool takes zero parameters, so the baseline is 4 and there is no argument semantics to explain. The description instead documents the shape of each returned row, including the status vocabulary (draft / in_review / live) and derived counters such as lessons with a ready video, which adds meaning beyond the empty schema.

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?

First sentence gives a specific verb and resource ('List the signed-in teacher's TT Uni courses') and enumerates the returned fields (id, title, status, kind, price_inr, lesson counts, public and Studio urls), which inherently separates this plural listing from the singular sibling tt_uni_get_course.

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 states the audience constraint clearly ('work only for approved TT Uni teachers') and redirects non-teachers to https://tradetron.tech/learn/teach, plus marks the call AUTH-REQUIRED. It does not explicitly contrast itself with tt_uni_get_course or state what to do when the teacher has no courses, so no full when/when-not routing is present.

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