Skip to main content
Glama

courses_save

Create a course (with its price; it starts as a draft) or edit one: details, price, watermark, publish or unpublish. Publishing needs a published lesson.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "courses_save"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description adds real behavior: newly created courses start as drafts, and publish/unpublish is a toggle gated on having a published lesson. It does not say whether an edit is a partial merge or a full replace, what happens to a draft's unpublished fields, or what permissions are required for a mutation.

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 sentences, both dense with distinct information: the first covers create/edit scope and the editable fields, the second covers the publish precondition. Nothing is repeated from the title and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, the description covers mode selection, draft-on-create behavior, and the publish gate. It leaves an agent unsure how the 'details, price, watermark' values are actually supplied, given the input schema declares no properties, and says nothing about the result of the operation or edit/overwrite semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero declared parameters the schema carries no semantics, so the baseline is 4; the description does supply field-level meaning (price at creation, watermark, publish state) that an agent could not derive from an empty object schema. The caveat is that the schema exposes no properties at all, so the description's field vocabulary is not anchored to any actual argument names.

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 gives a specific verb pair and resource ('Create a course ... or edit one') plus the editable surface (details, price, watermark, publish/unpublish), which cleanly separates it from the read-only siblings courses_get and courses_list. It stops short of naming those siblings explicitly, so differentiation is inferred from naming conventions rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It distinguishes the two modes (create vs. edit) and flags one hard precondition: 'Publishing needs a published lesson.' That is genuinely useful routing information, but there is no explicit when-not guidance, no mention of what to call first (e.g., a course-outline or lesson tool), and no statement about which sibling to use for reading a course.

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