Skip to main content
Glama
Sign In
Frappe LMS MCP Server

Frappe LMS MCP Server

by anggun-indra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_course

Remove a course and all its chapters, lessons, and enrollments by providing the course slug.

Instructions

Delete a course and all its chapters, lessons, and enrollments.

Args: course: The course name (slug).

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": {
      "course": "<course>"
    },
    "name": "delete_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description discloses cascading deletion, which is critical. However, it lacks details on permission requirements, irreversibility, or error cases. Does not contradict annotations (none provided).

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?

The description is two sentences: first states the action and scope, second describes the parameter. It is front-loaded and concise without waste.

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

Completeness3/5

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

While the description covers the core action and cascading, it omits return value (output schema exists but not described) and does not warn against alternatives. Given the complexity, more detail on return and when to use granular deletion would help.

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 0%, so the description must compensate. It explains that 'course' is a slug, adding meaning beyond the schema's 'string' type. But it does not specify format or constraints beyond that.

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 states 'Delete a course and all its chapters, lessons, and enrollments.' It uses a specific verb (Delete) and resource (course) and distinguishes from sibling tools like create_course, update_course, and publish_course.

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?

The description implies usage through the name and cascading effect, but does not explicitly state when to use this tool versus alternatives like delete_chapter or delete_lesson. No guidance on prerequisites or when not to use.

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