Skip to main content
Glama

course_outline_save

Replace a course outline: modules and lessons in order (video, text in Markdown, or file). Omitted modules and lessons are removed. Attach uploaded videos and files by asset id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "course_outline_save"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior2/5

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

The description does useful behavioral work by disclosing that omitted modules and lessons are removed, which is exactly the kind of data-loss context annotations rarely convey. That disclosure conflicts with destructiveHint=false, since a full replace that deletes omitted lessons is a destructive update to the existing resource.

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?

Three short sentences, front-loaded with the operation and followed by the destructive consequence and the asset-attachment rule. No filler or redundant restatement of the title.

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 mutation tool with no output schema, the description covers what is written, what is destroyed, and how uploaded assets are referenced. The remaining gap is the total absence of parameter names or a payload shape against an empty input schema, which an agent needs to actually invoke it.

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?

With zero declared parameters, the schema tells an agent nothing about input shape, and the description is the only source of meaning: ordering, content types, and attaching assets by id. Yet it still gives no parameter names, nesting structure, or asset-id format, so an agent cannot construct the payload from this definition alone.

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 names a specific verb and resource ('Replace a course outline') and enumerates the constituent content types (modules, lessons, video, Markdown text, file). It does not differentiate this tool from close siblings such as courses_save, so an agent must infer that this one is outline-specific.

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?

'Replace' plus 'Omitted modules and lessons are removed' implies the full-overwrite usage pattern and rules out incremental editing, which is useful implied guidance. However, it never states when an agent should prefer a different tool (e.g., courses_save) or what prerequisites/permissions are needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources