Skip to main content
Glama

Start a lesson

start_lesson

Start a guided study session on a learner's chosen topic; the topic becomes their first message, and lessons can be tied to a space so facts are saved to its knowledge graph.

Instructions

Start a new study session in godspeed taught by you: you teach what is new and give problems on what needs practice. The topic becomes the learner's first message. With space_id the lesson belongs to that space: it opens with the space's card and its facts go into that space's graph. In a prep, a topic named exactly like one on its sheet counts for that topic. You teach it through wait_for_work; the learner follows along in the godspeed window.

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": {
      "topic": "<topic>"
    },
    "name": "start_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhat the learner wants to study, in their words.
space_idNoThe space id from list_spaces, or "none" for lessons without a space (the default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior4/5

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

The annotations cover mutation safety, and the description adds meaningful behavior: the topic becomes the learner's first message, space_id ties the lesson to a space and its graph, prep topics match by exact name, and teaching runs through wait_for_work. It does not discuss failure modes or permissions, but the key side effects are disclosed.

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 description is front-loaded and every sentence is relevant to starting or conducting a lesson. It is somewhat dense, especially the prep-matching sentence, but not padded.

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 two-parameter session-start tool with annotations and full schema coverage, it explains the lifecycle, space effects, prep matching, and next step through wait_for_work. Minor omissions such as return behavior are acceptable because there is no output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds semantic effects beyond the schema: topic becomes the learner's first message, and space_id determines the lesson's space, card, and graph destination.

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?

States a specific verb and resource: start a new study session in godspeed taught by the agent. It also differentiates from read/list siblings by describing session creation rather than retrieval.

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?

Implies when to use it, namely to begin a study session, and points to wait_for_work for the teaching loop. However, it does not explicitly state when not to use it or name alternative tools for starting or resuming study.

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