Skip to main content
Glama

Create complete course draft

create_course_from_blueprint
Idempotent

Starts an unpublished, resumable Trainn course build from a complete one-time blueprint. Call only when the user has explicitly asked to create, build, import, or push the course to Trainn. Do not call while the user is only planning. This creates the course and its initial chapters and lessons, persists source and dependency instructions for the initial build, and never publishes. Continue with get_course_build_status and its next_tool values until the build can be handed off. Ask the user only for genuinely missing files, permissions, or material ambiguities.

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>",
      "spec_version": "<spec_version>",
      "course": "<course>",
      "sources": "<sources>",
      "blueprint": "<blueprint>",
      "chapters": "<chapters>"
    },
    "name": "create_course_from_blueprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes
sourcesYesInspected evidence used by this initial build. Use [] only when the user explicitly authorized general knowledge.
chaptersYes
blueprintYes
spec_versionYesAlways 1.
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), it discloses that the result is an unpublished, resumable build that creates initial chapters and lessons, persists source and dependency instructions, and never publishes. It also bounds user prompting to genuinely missing files, permissions, or material ambiguities — behavior an agent could not infer from the structured fields.

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?

Front-loaded with purpose, then the invocation gate, then the behavior, then the continuation path, then the prompting constraint. Every sentence carries operational information; none restate the tool title.

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

Completeness5/5

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

For a six-required-parameter, deeply nested creation tool with no output schema, the description covers the full lifecycle: what is created, that it stays unpublished and resumable, how to poll progress, and when to interrupt the user for input. Nothing an agent needs to invoke it correctly is missing.

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?

Top-level schema description coverage is only 33%, but the nested schema is unusually detailed, and the description adds the requirement that the blueprint be complete and that source/dependency instructions persist for resumption. It does not explain idempotency_key or spec_version semantics, which is the main remaining gap given the low top-level coverage.

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 ('Starts an unpublished, resumable Trainn course build from a complete one-time blueprint') and the qualifier 'complete one-time blueprint' implicitly separates it from the draft-oriented siblings such as create_course_draft. An agent can tell what this produces without opening the 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?

Explicit invocation gate: only when the user has asked to create, build, import, or push the course, and explicitly not while the user is only planning. It also names the follow-up path (get_course_build_status and its next_tool values) so the agent knows what to do after the call rather than hunting for an alternative.

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