Skip to main content
Glama

Read a lesson

read_lesson
Read-onlyIdempotent

Read a lesson as markdown, including dialogue, quizzes, and answers; long lessons return in numbered pages so you can retrieve the full content.

Instructions

Read one lesson as markdown: everything the teacher and learner said, quizzes and answers included. A long lesson comes in pages; each page says which page it is and how many there are.

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

Input Schema

NameRequiredDescriptionDefault
pageNoThe page to read (default 1).
lesson_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description adds genuinely new behavior: results are paginated, each page self-reports its index and total, which tells the agent how to iterate. It stops short of stating anything about error cases or missing lessons.

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

Conciseness5/5

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

Two short sentences with no filler: the resource and payload come first, the pagination caveat second. Every clause carries information an agent needs.

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 carries the burden of return values and does so well, describing both the markdown body and the page envelope. The remaining gap is the undocumented `lesson_id` parameter and no pointer to list_lessons for discovering one.

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%: `page` is documented in the schema with a default of 1, while `lesson_id` has no description anywhere. The description's paging sentence adds real meaning about how `page` behaves in practice, but it never names the parameter or explains what a lesson_id is or where to get one.

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 gives a specific verb and resource ('Read one lesson as markdown') and scopes the content ('everything the teacher and learner said, quizzes and answers included'), so an agent knows exactly what comes back. It does not explicitly distinguish itself from siblings like read_passage or read_work, which keeps it just below a 5.

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 is only implied: the paging note tells the agent how to consume long results, but there is no statement of when to prefer this over read_passage, read_work, or list_lessons, and no precondition such as obtaining a lesson_id. Adequate but with clear guidance gaps.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.