Skip to main content
Glama

Get course build status

get_course_build_status
Read-only

Resumes an active initial course build created from a one-time blueprint. While build.state is building, follow progress.lessons and course_completion next_tool values in order. Once the build is completed or superseded, its blueprint is audit provenance only and progress reflects the live draft; use get_course_draft and targeted CRUD tools for later edits.

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>"
    },
    "name": "get_course_build_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real value: it names response fields (build.state, progress.lessons, course_completion.next_tool) and explains lifecycle semantics — that after completion the blueprint becomes audit provenance while progress tracks the live draft. It does not explain the non-idempotent nature (status changing between calls), which would have been worth stating.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Two dense sentences that front-load the resource scope and then route the agent to later-phase tooling; almost no waste. Some phrasing ('audit provenance only', 'superseded') is terse jargon that slows first-pass comprehension.

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?

With no output schema, the description carries the burden of explaining return values, and it does so at a high level by naming build.state and the progress/next_tool fields and describing how they should be consumed. It stops short of the full response shape, but for a single-parameter status tool this is close to sufficient.

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?

There is one parameter (course_id) with 0% schema description coverage, and the description never mentions it — no indication of the accepted course id form or whether it must be the original blueprint-derived course. The name is self-explanatory enough that the gap is minor, but the description does not compensate for the coverage gap as the rubric requires for low-coverage schemas.

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 anchors the tool to a specific resource state ('an active initial course build created from a one-time blueprint') and explicitly contrasts it with get_course_draft. The opening verb 'Resumes' is a poor fit for a status getter, however, and the actual act of returning build state has to be inferred from 'follow progress.lessons and course_completion next_tool values.'

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?

Gives a concrete use condition ('While build.state is building') and a concrete stop condition with alternatives ('Once the build is completed or superseded ... use get_course_draft and targeted CRUD tools'). The only gap is that 'targeted CRUD tools' is left as a loose category rather than named siblings.

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