Skip to main content
Glama

TT Uni Save Chapter

tt_uni_save_chapter
Destructive

Add or edit a chapter (WRITES: creates one, or overwrites the fields you pass on an existing one). New chapter: course_id + title. Edit: chapter_id + new title and/or position (1-based order).

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

Input Schema

NameRequiredDescriptionDefault
titleNo
positionNo
course_idNo
chapter_idNo

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?

Annotations already declare a destructive, non-idempotent write, and the description adds real context on top: it clarifies that only the fields passed are overwritten on an existing chapter, that everything stays a draft until TT Uni review approves it, and that auth is required. It also discloses the review-team gate and content rules that constrain what may be written.

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?

The opening sentences are front-loaded and precise, with the write semantics and mode split stated first. The trailing teaching-rules and INR/GST pricing block is boilerplate shared across the TT Uni family and is only loosely relevant to saving a chapter.

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?

For an auth-gated draft-writing tool, the description covers who may call it, what state the result is in, and which parameter combinations mean create vs edit. It does not say what the response contains (e.g., the resulting chapter_id), which a caller may need to chain further edits.

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

Parameters5/5

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

Schema description coverage is 0% and all four parameters are optional, so the description carries the full burden — and it does, mapping each parameter to its role (course_id + title to create; chapter_id + title/position to edit) and explaining that position is a 1-based order.

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?

The first sentence gives a specific verb and resource ('Add or edit a chapter') and immediately disambiguates the two modes: create via course_id + title, edit via chapter_id + title/position. An agent can tell this handles chapters rather than the sibling save_lesson/save_cohort/save_session resources.

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?

Explicit when-to-use guidance for both modes ('New chapter: course_id + title. Edit: chapter_id + new title and/or position'), plus the constraint that the caller must be an approved TT Uni teacher. It does not name an alternative tool or state when not to use this one, so it stops short of a 5.

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