Skip to main content
Glama

TT Uni Delete

tt_uni_delete
DestructiveIdempotent

Delete a course, chapter, lesson or session the teacher owns. kind = course | chapter | lesson | session. A course can be deleted only while it is a draft with no learners. Not recoverable through this server: confirm with the teacher, naming the item, before calling.

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": {
      "kind": "<kind>",
      "item_id": "<item_id>"
    },
    "name": "tt_uni_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYescourse | chapter | lesson | session
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, but the description adds material context beyond them: the deletion is not recoverable through this server, the draft-only/no-learners constraint on courses, the confirmation ritual, and the auth/teacher-approval requirement. That is exactly the behavioral load a destructive tool needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first paragraph is well front-loaded and entirely relevant, but roughly two-thirds of the text is TT Uni marketplace boilerplate (teaching rules on tips, P&L screenshots, 30-day market data, INR/GST pricing, 50% revenue split) that has no bearing on deleting an item and dilutes the operative constraints.

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 a two-parameter destructive tool with annotations covering the safety profile, the description supplies the essentials: ownership scope, draft-only restriction, irreversibility, and confirmation. It omits cascade behavior (what happens to chapters/lessons/sessions when a parent course or chapter is deleted) and any return value, which matters for a destructive operation.

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 coverage is 50%: the schema already documents 'kind' as course | chapter | lesson | session, and the description merely restates it. 'item_id' is left unexplained in both places — no hint about its format or where to obtain it — though the confirmation instruction ('naming the item') gives indirect signal about its role.

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?

Opens with a specific verb plus resource ('Delete a course, chapter, lesson or session') and scopes it to items 'the teacher owns', which cleanly separates it from the tt_uni_save_* and tt_uni_update_course siblings. The four valid kinds are enumerated immediately, so an agent knows exactly what this tool operates on.

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 concrete preconditions: a course may be deleted only while it is a draft with no learners, the caller must be an approved TT Uni teacher, and the agent should confirm with the teacher naming the item before calling. It does not name a sibling alternative (e.g., unpublish/update) for the non-draft case, leaving that path to inference.

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