Skip to main content
Glama

TT Uni Course Format

tt_uni_course_format
Read-onlyIdempotent

Return the TT Uni course markdown format and the authoring prompt. Call this FIRST when a teacher wants to design a course with you: plan the course with them, write it in this format, show it, then create it with tt_uni_create_course. Front matter (title, summary, kind, price, level, topics, prerequisites, outcomes, cover), description, ## Chapter: ..., ### Lesson: ..., optional id: / video: / preview: yes lines under a heading.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the bar is lower, and the description still adds real context: AUTH-REQUIRED, teacher-only access, and DRAFTS ONLY with no publication until the review team approves. Marketplace rules (no tips/calls, no promised returns, 30-day-old data, disclosure of paid strategies) and INR pricing with 18% GST and 50% revenue share go well beyond annotations, though it doesn't describe the shape or size of the returned prompt/content.

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 the call-first directive, then the format spec, then policy/pricing context. The second paragraph is dense but each clause (auth, drafts only, teaching rules, GST/revenue split) carries distinct operational weight rather than restating annotations.

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 and no parameters, the description correctly carries the burden of explaining what comes back, and it does so at a structural level. The 'authoring prompt' is named but never characterized, and nothing indicates how long the returned format is or whether it is static across calls.

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. The description usefully previews the structure of the returned document (front matter keys, chapter/lesson headings, optional per-heading lines), which is the closest thing to parameter guidance this tool needs.

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 concrete verb and resource — returns the TT Uni course markdown format plus the authoring prompt — and enumerates what the format contains (front matter fields, description, `## Chapter:`/`### Lesson:` headings, optional id/video/preview lines). It is clearly separable from the write-side siblings such as tt_uni_create_course.

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?

Explicitly says to call this FIRST when a teacher wants to design a course, then lays out the sequence: plan with the teacher, write in this format, show it, then create it with tt_uni_create_course. It also states the eligibility precondition (approved TT Uni teachers only) and where non-teachers are redirected.

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