Skip to main content
Glama

Duplicate course

duplicate_course
Idempotent

Starts an asynchronous copy of an existing Academy course. Poll get_course_duplication_status until it succeeds or fails.

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": {
      "source_course_id": "<source_course_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "duplicate_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
idempotency_keyYes
source_course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, and the description adds the genuinely useful fact that the operation is asynchronous and must be polled rather than returning a finished copy. It stops there, though: it never says what the duplicate contains (draft vs. published state), how long the job typically takes, or how errors surface, which matters for a non-reversible-seeming bulk copy.

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?

Two short sentences, action first, follow-up second; no filler, no restatement of the title.

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?

Given an async mutation with no output schema, the description correctly tells the agent that nothing is returned synchronously and names the polling tool, which is the missing piece that would otherwise cause misuse. It falls short only on the undocumented idempotency_key and on what the resulting copy is.

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?

Schema description coverage is 0% for both parameters and the description does not compensate. source_course_id is only loosely implied by "an existing Academy course," and idempotency_key — the parameter most likely to be misused — is never mentioned, despite the annotation flagging the call as idempotent.

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?

Names a specific verb and resource ("Starts an asynchronous copy of an existing Academy course") and pairs it with the exact follow-up tool, get_course_duplication_status, so the agent can distinguish it from create_course_draft or create_course_from_blueprint without opening a schema.

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 explicit workflow guidance: call this to start, then poll get_course_duplication_status until success or failure. It lacks a when-not-to-use statement against the other course-creation siblings (create_course_draft, create_course_from_blueprint), which would be the natural discriminator for an agent choosing between them.

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