Skip to main content
Glama

Create course shell

create_course_draft
Idempotent

Creates an unpublished metadata-only course shell when the user explicitly requests an empty, minimal, or step-by-step course. For a normal request to build a useful first draft, use create_course_from_blueprint instead. This never creates structure, content, or a publication.

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": {
      "idempotency_key": "<idempotency_key>",
      "title": "<title>"
    },
    "name": "create_course_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
metadataNo
settingsNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds valuable negative scope — the shell is unpublished and never creates structure, content, or a publication — which prevents an agent from assuming it builds a usable course. It omits permission requirements and what identifier comes back, so it is not fully rich.

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 sentences, front-loaded with scope, then the alternative, then the negative guarantee. No filler or restatement of the title.

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?

The critical routing ambiguity is fully resolved, but with no output schema the description should still tell the agent what handle it receives back to continue with update_course_draft or apply_course_structure, and it should justify the mandatory idempotency_key. Those gaps leave an agent under-informed about the full create-then-build workflow.

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?

Top-level schema description coverage is 0%: title, metadata, settings and idempotency_key have no descriptive text. The description hints at metadata ('metadata-only') but says nothing about settings (nested certification/seek/lesson-jump options) or why idempotency_key is required, so it fails to compensate for the coverage gap despite the nested properties being self-documented.

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?

States a specific verb and resource ('Creates an unpublished metadata-only course shell') and immediately distinguishes it from the sibling that builds a populated draft. An agent can tell exactly which create tool to pick without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger (user explicitly requests an empty, minimal, or step-by-step course) and an explicit alternative with its own trigger ('For a normal request to build a useful first draft, use create_course_from_blueprint instead'). Both the when and the when-not are covered.

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