Skip to main content
Glama

Get lesson insights

get_lesson_content_insights
Read-only

Returns bounded, permission-scoped context for a lesson video, article, guide, or embed so the AI can improve lesson copy or generate grounded quiz questions. Video context includes its transcript when ready.

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>",
      "lesson_id": "<lesson_id>"
    },
    "name": "get_lesson_content_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
lesson_idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, closed-world), so the description is not obligated to restate them. It does add genuinely useful behavior beyond that: the payload is bounded and permission-scoped, and video transcripts are only present "when ready", which warns the agent about partial results.

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?

Two sentences, front-loaded with the return semantics before the motivation, with no filler. "Bounded" and "permission-scoped" are compact and informative, though "bounded" stays undefined (no size or truncation hint).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does some work by naming what comes back for videos (the transcript, when ready), but it leaves the overall response shape, truncation behavior, and the meaning of the two required identifiers unstated. Adequate for a simple two-parameter read, but there are clear gaps an agent would hit on first call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden of explaining course_id and lesson_id, and it says nothing about either. The names are largely self-explanatory and both are required, which limits the damage, but no format, source, or relationship between the two identifiers is given.

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 uses a specific verb ("Returns") and a clearly scoped resource ("bounded, permission-scoped context for a lesson video, article, guide, or embed"), and it enumerates the supported content types. It implicitly separates itself from the write-side siblings (upsert/attach/remove_lesson_content) by being a read of lesson content, though it never names an alternative.

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?

It gives a use case ("so the AI can improve lesson copy or generate grounded quiz questions"), which is more than nothing, but there is no explicit when-not-to-use guidance and no named alternative for cases like checking upload or import state. The agent must infer that this is the read path versus the sibling write/status tools.

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