Skip to main content
Glama

save_lesson_draft

Write one lesson's markdown content to disk. Provide course slug, lesson id, and markdown with required sections.

Instructions

Step 5 — Save a drafted lesson file.

Write one lesson's markdown content to disk. Call once per lesson.
The lesson_id must match an id in lessons.json (e.g. "lesson-01").

The lesson MUST include these sections in order:
  ## Learning objectives
  ## Prerequisites
  ## Content  (with ### Section N: subsections)
  ## Summary
  ## Exercises
  ## Further reading

Args:
    slug: The course slug.
    lesson_id: The lesson id from lessons.json (e.g. "lesson-01").
    content: Full markdown content of the lesson.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
lesson_idYes
contentYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Without annotations, the description must fully disclose behavior. It states 'writes to disk' but omits details like overwrite behavior, file path conventions, or if validation of required sections occurs. No mention of error handling or return value. This leaves significant gaps for a mutation tool.

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?

Well-organized: a heading, purpose statement, usage note, section requirements, and parameter list. Sentences are efficient and front-loaded. Could omit 'Step 5' if not widely understood, but it's not wasteful.

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?

Given the output schema exists (true), the description covers purpose, required sections, and parameter roles. It explains the tool's place in the workflow (step 5) and constraints. With simple params and no nested objects, this is nearly complete, though return behavior is absent.

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 0%, so description adds value by naming parameters and specifying lesson_id must match lessons.json. Content is described as 'Full markdown content'. However, slug lacks format constraints, and content's required sections are given but not tied to validation. Modest improvement over bare schema.

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 clearly states the tool saves a lesson draft file to disk, specifying it's step 5 and for a single lesson. It distinguishes from sibling tools like save_course_curriculum or save_course_outline by focusing on lesson content. However, it could more explicitly differentiate its role in the course-building workflow.

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?

Provides usage constraints: call once per lesson, lesson_id must match lessons.json, and required sections. But lacks guidance on when not to use it or alternatives among siblings like save_course_sources or publish_course. The when-to-use context is implicit but not explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server