Skip to main content
Glama

Опубликовать курс

publish_course
Destructive

Открывает курс ученикам или возвращает в черновики. Публикация идёт через лимит тарифа — ту же проверку, что кнопка в кабинете: считаются только опубликованные курсы, черновики нет. Если лимит исчерпан — 409 с текстом, что делать. Курс из архива не публикуется, тоже 409: сначала его возвращают в работу в кабинете. Снять с публикации можно всегда.

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": "publish_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
publishedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses the tariff-limit check, the counting rule (only published courses count, drafts do not), and two distinct 409 failure modes with remediation guidance — genuinely useful behavior an agent cannot infer. The one tension is that annotations declare idempotentHint=false while the described set-state semantics look idempotent; the description does not resolve this, so it stops short of 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.

Conciseness4/5

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

Four sentences, all information-bearing, with the core action front-loaded before the limit and archive caveats. Dense but well ordered; nothing is padding, though the 409 discussion could be tightened slightly.

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 mutating, non-read-only tool with an output schema absent and annotations covering the safety profile, the description supplies the failure modes, limit semantics, and the archive restriction an agent needs to act. Missing only auth/permission expectations and any hint of the success response.

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 parameter meaning. It does convey the publish/unpublish duality that maps onto `published`, but never names the parameter, never mentions that `published` defaults to true, and leaves `course_id` entirely unexplained. Partial compensation only.

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?

The description opens with a precise verb+resource pair and covers both directions of the operation ('opens the course to students or returns it to drafts'), which is exactly the toggle exposed by the `published` parameter. It is unmistakably not create_course, get_course, or list_courses, so an agent can select it without opening the 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?

It states the conditions under which the tool must not be used (archived course — must first be restored in the dashboard) and the condition under which publishing fails (tariff limit exhausted), plus that unpublishing is always permitted. It gives clear context and one hard exclusion, but does not name any sibling tool as an alternative path.

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