Skip to main content
Glama

TT Uni Test Stats

tt_uni_test_stats
Read-onlyIdempotent

How the tests (quizzes) in one of the teacher's courses are doing. Per test: learners who tried it (and how many are enrolled), attempts, passed, pass_rate, first_try_pass_rate, avg_best_score (0-1), most_missed (question number, text, share who missed it) and question_detail (every question's miss rate). Miss rates use each learner's FIRST try on the current version of the test; a question most learners miss usually means the lesson before it needs a clearer explanation. Aggregates only, never learner names. Same numbers as the Studio dashboard's Tests tab.

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

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world); the description adds real behavior beyond them: aggregates only with no learner names, and miss rates computed from each learner's FIRST attempt on the current test version. It also flags AUTH-REQUIRED and teacher-approval gating. It doesn't state error behavior for a course the caller doesn't own.

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 first paragraph is dense but front-loaded and every clause about metrics and first-try semantics earns its place. The second paragraph is boilerplate policy (TT Uni marketplace pitch, pricing in INR/GST, 50% revenue share, content rules) that is largely irrelevant to a read-only stats lookup and dilutes the signal.

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 properly documents the return shape field by field, and it states the auth/approval prerequisite. For a single-parameter read-only report this is close to sufficient; only ownership/error semantics for course_id are missing.

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?

One required parameter at 0% schema coverage, so the description must carry the load. 'One of the teacher's courses' implies ownership scoping but never explains what course_id is, its type, or what happens if it belongs to another teacher.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific resource and scope — quiz/test performance for one of the teacher's own courses — and enumerates the exact metrics returned (attempts, passed, pass_rate, avg_best_score, most_missed, question_detail). It reads as a reporting tool, clearly distinct from the authoring siblings (save_lesson, submit_for_review), though it never names a sibling to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: the audience restriction (approved TT Uni teachers only) and 'same numbers as the Studio dashboard's Tests tab' hint at when it applies, but there is no explicit when-to-use/when-not or alternative tool named for cases like 'all my courses' or 'one learner's results'.

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