Skip to main content
Glama
Sign In
MCPaeroedu

MCPaeroedu

Official
by aerovfx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

aeroedu_chapter_add

Add a new chapter to an existing course by providing the course ID and chapter title. Optionally specify the order and description to structure the course content.

Instructions

Thêm 1 chương mới vào khoá học. Trả về chapter_id để dùng cho aeroedu_lesson_add.

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_id": "<course_id>",
      "title": "<title>"
    },
    "name": "aeroedu_chapter_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYescourseId từ aeroedu_course_create hoặc aeroedu_course_list
titleYesTên chương
orderNoThứ tự (1-based). Bỏ trống = thêm cuối
descriptionNoMô tả chương

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior3/5

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

Annotations show it's a write operation (readOnlyHint=false) but provide no other behavioral details. The description adds that it returns chapter_id but does not mention side effects, error conditions, or prerequisites beyond the schema.

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?

Two concise sentences front-load the purpose and output usage with no extraneous information.

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 simple creation tool, the description covers purpose and output. It lacks error handling details but is sufficient given the tool's simplicity and the absence of an output schema.

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 100% with descriptions for all parameters. The description does not add additional meaning to the parameters beyond what the schema provides.

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 tool adds a new chapter to a course, specifies the return value (chapter_id) for use with aeroedu_lesson_add, and differentiates from sibling tools like aeroedu_block_add_* and aeroedu_lesson_add.

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

Usage Guidelines4/5

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

It explicitly says when to use (to add a chapter) and mentions the next step (aeroedu_lesson_add). While it doesn't explicitly state when not to use or list alternatives, the context from siblings makes the usage clear.

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