Skip to main content
Glama
Sign In
Frappe LMS MCP Server

Frappe LMS MCP Server

by anggun-indra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_lesson

Remove a lesson from a chapter in a Frappe LMS course. Specify the lesson and chapter names to delete the lesson and update the chapter.

Instructions

Delete a lesson and remove it from the chapter.

Args: lesson: The lesson name. chapter: The chapter name.

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": "<lesson>",
      "chapter": "<chapter>"
    },
    "name": "delete_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
lessonYes
chapterYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavior. It states deletion and removal from chapter but does not discuss irreversibility, effects on related content (e.g., quizzes, paragraphs), or required permissions.

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

Conciseness3/5

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

The description is concise but lacks structure. It front-loads the main action and then lists parameters, but it omits important details that could be added without significant verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and many sibling tools, the description fails to explain return values, error conditions, or side effects. It is insufficient for safe and effective usage.

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?

Schema coverage is 0% (no descriptions in schema). The description adds that 'lesson' and 'chapter' are names, which provides minimal extra meaning beyond the schema's type definitions.

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?

The description clearly states the action (delete) and the resource (lesson), specifying that it removes the lesson from the chapter. It effectively distinguishes itself from sibling tools like create_lesson, update_lesson, and move_lesson.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as delete_chapter or other mutation tools. There are no preconditions or exclusions mentioned.

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

Deploy Server

Other Tools