Skip to main content
Glama
Sign In
Frappe LMS MCP Server

Frappe LMS MCP Server

by anggun-indra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reorder_chapter

Move any chapter to a new position in your course outline by specifying the course, chapter, and desired index.

Instructions

Move a chapter to a new position in the course outline.

Args: course: The course name (slug). chapter: The chapter name. idx: New 0-based position.

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>",
      "chapter": "<chapter>",
      "idx": "<idx>"
    },
    "name": "reorder_chapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
idxYes
courseYes
chapterYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided; description does not disclose side effects (e.g., whether other chapters shift, permission requirements, or reversibility). It only states the basic action, lacking behavioral context 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?

Description is concise with no wasted words, but the Args block is somewhat redundant with the schema. Front-loaded sentence is clear. Overall efficient.

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?

Provides parameter explanation but omits behavioral details (e.g., impact on other chapters, permissions). Output schema exists but description doesn't mention return value. Adequate for basic use but not fully complete.

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?

Despite 0% schema description coverage, the description adds meaning: course is 'slug', chapter is 'name', idx is 'new 0-based position'. This clarifies the parameters beyond the bare schema names.

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?

Description clearly states 'Move a chapter to a new position in the course outline', identifying specific verb (move), resource (chapter), and context (course outline). This distinguishes it from sibling tools like update_chapter or delete_chapter.

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?

No explicit guidance on when to use vs alternatives or prerequisites. The description states what it does but not when it should be chosen over other tools like move_lesson or update_chapter. Usage is implied but not clarified.

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