Skip to main content
Glama

Get course draft

get_course_draft
Read-onlyIdempotent

Returns the canonical course state used by the next draft write, including authors, course_id, and expected_revision. Use it when the caller does not already have a fresh mutation response.

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_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It does: the notion of 'canonical course state' plus 'expected_revision' signals that the response carries concurrency metadata intended to be fed into a subsequent write, which is value beyond the annotations. Auth requirements and response shape details are absent, keeping it below a 5.

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 with zero padding: the return content is front-loaded and the usage condition follows immediately. Every clause carries information.

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?

For a one-parameter read tool with no output schema, the description supplies enough to call it correctly and to understand what comes back ('including...' lists the salient fields). It stops short of describing pagination, error cases, or the full response shape, but none of those are essential here.

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% for the single parameter, so the description should compensate. It mentions course_id only as part of the returned state, not as the input selector, leaving the meaning of the input argument to the parameter name alone. The name is self-evident, so this is adequate but not additive.

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 states a specific verb and resource ('Returns the canonical course state') and enumerates the key returned fields (authors, course_id, expected_revision), which is far more than a restatement of the name. It does not name a sibling tool outright, but the phrase 'used by the next draft write' implicitly separates it from create_course_draft/update_course_draft.

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?

It gives an explicit selection condition: use this tool 'when the caller does not already have a fresh mutation response.' That is clear positive guidance, though it never states a when-not condition or names a specific alternative sibling to use in the complementary case.

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