Skip to main content
Glama

Attach lesson content

attach_lesson_content
DestructiveIdempotent

Attaches visible, ready Trainn Library content. During an active initial build, pass its build id as approved_build_id when the persisted blueprint selected this exact item. Otherwise call inspect_library_content and pass selection_token. If content already exists, stop and ask the user before retrying with the returned replacement confirmation token and a new idempotency key.

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>",
      "lesson_id": "<lesson_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "source": "<source>"
    },
    "name": "attach_lesson_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesAccepts one of the documented argument shapes.
course_idYes
lesson_idYes
idempotency_keyYes
expected_revisionYes
replacement_confirmation_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

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

The description adds real value beyond the annotations: it discloses the conflict-on-existing-content behavior, the replacement_confirmation_token retry path, and the need for a fresh idempotency key on retry, consistent with destructiveHint=true and idempotentHint=true. However, it never states what actually gets destroyed or overwritten on the lesson, nor what the replacement confirmation token represents in the response, leaving the destructive semantics underspecified.

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?

Four sentences, dense but front-loaded with the core action before the branching paths. Each sentence carries procedural content, though the final retry sentence packs three separate requirements (stop, replacement token, new idempotency key) into one hard-to-parse clause.

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 destructive, idempotent attach operation with no output schema and thin schema coverage, the description covers the essential decision tree: which source proof to supply, when to stop, and how to retry. Remaining gaps are the meaning of expected_revision and the success return shape, which are minor relative to what is provided.

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 only 17% schema description coverage across 6 parameters (5 required), the description does explain the two mutually exclusive source shapes via approved_build_id versus selection_token and covers idempotency_key rotation on retry. It says nothing about expected_revision (whose purpose is opaque from both schema and description) and nothing about the nested content_type/content_id pairing. Partial compensation, so a middling score.

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?

States a specific verb and resource: 'Attaches visible, ready Trainn Library content' to a lesson. It also names inspect_library_content as the prerequisite step, which distinguishes the flow from a plain content write. It does not differentiate against close siblings like upsert_lesson_content or import_lesson_content, which could plausibly be confused with attaching.

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 branching guidance: use approved_build_id when a persisted blueprint selected this exact item during an active initial build; otherwise call inspect_library_content and pass selection_token. It also gives an explicit stop condition — if content already exists, stop and ask the user before retrying — which is exactly the when-not guidance an agent needs for a destructive write.

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