Skip to main content
Glama

Finish initial course build

finish_course_build
Idempotent

Ends the one-time initial build and makes the live Trainn draft the sole authority for future edits. Use outcome completed only after every planned lesson is complete and readiness has no blocking errors. Use superseded when the user intentionally changed the course in Trainn or chat and wants to continue from the current draft instead of the original blueprint. Never publishes.

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>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "outcome": "<outcome>"
    },
    "name": "finish_course_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcomeYes
course_idYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the state transition itself: the blueprint stops being authoritative and the live draft becomes the sole source of future edits, and the tool never publishes. What is not disclosed is failure behavior, e.g. what happens when expected_revision is stale or when the readiness check fails at call time. That gap keeps it below a 5 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each doing distinct work: purpose, then one sentence per outcome value, then the non-publishing boundary. The most important state-change clause is front-loaded in sentence one.

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 decision guidance an agent needs to choose this tool and pick an outcome is complete, and there is no output schema to explain. However, for a required-argument state transition with no output schema, the description says nothing about expected_revision conflict handling, idempotency_key reuse semantics, or what the caller observes on failure - information not available anywhere else in the definition.

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 description coverage is 0%, so the description must carry all parameter meaning, and it only covers outcome, explaining the two enum values in operational terms. course_id, expected_revision (a concurrency token) and idempotency_key (a dedupe key, maxLength 200) are left entirely undefined, so an agent must guess how to construct or source them.

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 ('Ends the one-time initial build') plus the resulting state change ('makes the live Trainn draft the sole authority for future edits'). The closing 'Never publishes' explicitly fences it off from publish_course, so an agent can distinguish it from the nearest sibling without opening schemas.

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 explicit selection rules for both enum values: 'completed only after every planned lesson is complete and readiness has no blocking errors', and 'superseded when the user intentionally changed the course in Trainn or chat'. It also names the excluded case ('Never publishes'), so when-not is covered as well as when.

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