Skip to main content
Glama

Axad

Open a lesson

open_lesson
Idempotent

Open a lesson and read where the learner is in it: a lesson of Axad's library (lesson), one the learner already has (material), or a new lesson made from a text they supply (text). Returns the current page's text or the first 40 sentences, and starter suggestions. It counts as one of the plan's active lessons until closed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWith text: BCP 47 code of the text's language.
textNoThe learner's own text to study: an article, a letter, a message.
titleNoWith text: a short title in the text's language.
lessonNoA lesson id from Axad's library.
materialNoA material id of a lesson the learner already has.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lesson / description
      Previous value: -"A lesson id from browse_catalog."New value: +"A lesson id from Axad's library."
    • changedInput schema / properties / material / description
      Previous value: -"A material id from list_lessons or an earlier open_lesson."New value: +"A material id of a lesson the learner already has."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations mark this as a non-read-only but idempotent, non-destructive operation, and the description supplies the missing reason: opening consumes a slot among the plan's active lessons until closed. It also discloses what is returned (current page text or first 40 sentences, plus starter suggestions), which is valuable given there is no output schema. It does not say what happens when the active-lesson capacity is exceeded or when the same lesson is re-opened.

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?

The core action and its side effect are front-loaded, and the parenthetical mode list packs three alternatives into one clause with no filler. The single long sentence carrying all three modes is dense and slightly harder to scan than a short bulleted break would be.

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 5-parameter, 0-required tool with no output schema, the description covers the action, the three input modes, the return content, and the lifecycle side effect. Remaining gaps are edge-case behavior: which return shape applies to which mode, and how conflicting source parameters are resolved.

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 description coverage is 100%, so the parameter meanings are already documented; the description largely restates them while adding the useful signal that lesson, material, and text are alternative sources rather than combinable inputs. It adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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?

"Open a lesson and read where the learner is in it" states a specific verb plus resource, and the sentence then enumerates the three distinct sources (library lesson, existing material, supplied text). An agent can distinguish this from close_lesson or browse_catalog without opening the schema.

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?

The description clearly maps each of the three modes to its parameter and implies the mode is chosen by what the learner has on hand, plus the note that the lesson stays active until closed. It stops short of explicit routing such as "use browse_catalog to obtain a lesson id" or rules for what to do when several active lessons already exist.

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.