Skip to main content
Glama

Niche of One Network

Academy lesson

academy_lesson
Read-onlyIdempotent

Read one Academy lesson. Free lessons are open to anyone; member lessons say what unlocks them. Long text: best shown to the user as a document or artifact.

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": "<course>",
      "lesson": "<lesson>"
    },
    "name": "academy_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes
lessonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the free vs. member access gating and warns that responses can be long and are best rendered as a document or artifact, which an agent could not infer from the annotations.

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?

Three short sentences, no filler, with the core action front-loaded. The access sentence and the rendering hint are both useful, though the rendering advice is presentation guidance rather than invocation guidance.

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 simple two-required-parameter read tool with no output schema, the description covers purpose, access gating, and how to present long output. The remaining gap is identifier format for course and lesson, which is the one thing an agent could get wrong 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?

Both parameters (course, lesson) have 0% schema description coverage, so the description carries the full burden—and it says nothing about what form these identifiers take (slug, title, ID) or how they pair. The 2-param baseline of 4 is not available here because the schema is entirely undocumented.

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?

States a specific verb and resource: 'Read one Academy lesson', with 'one' clarifying this is a single-item read rather than a listing, which implicitly separates it from academy_browse. It stops short of naming an alternative explicitly, so it is clear but not fully sibling-differentiated.

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?

The description explains access conditions (free lessons open to anyone, member lessons state what unlocks them) but never says when to pick this over academy_browse or course, nor that lessons must presumably be discovered first. Usage is implied rather than prescribed.

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