Skip to main content
Glama

Delete Course

delete_course
Destructive

Soft-deletes an Orbits course after confirmation, removing it from listings; the API cannot restore it.

Instructions

(Admin) Borra un curso (soft delete: deja de aparecer; la API no permite restaurarlo). Pide confirmación.

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

Input Schema

NameRequiredDescriptionDefault
course_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavior: this is a *soft* delete where the course simply stops appearing, and there is no restore path via the API. The mention that confirmation is required is also useful operational context not present in the annotations.

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?

A single front-loaded sentence with the admin restriction first and the irreversibility caveat parenthesized. Every clause carries information; only the confirmation clause is too terse to be actionable.

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?

An output schema exists, so return values need not be explained, and the soft-delete and irreversibility semantics are well covered. The remaining gap is the confirm_token contract, which an agent cannot resolve from the definition alone on a destructive operation.

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%, so the description must carry the parameter burden. "Pide confirmación" hints that confirm_token exists but never explains what value to supply, its format, or where the token comes from, and course_id is left entirely undescribed — a real risk of mis-invocation on a destructive tool.

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 and resource ("Borra un curso") and immediately qualifies the operation as an admin-only soft delete. It is clearly distinguishable from update_course or delete_tag, but it does not name any sibling alternative, so it stops short of a 5.

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 states the prerequisite (Admin) and the confirmation requirement, plus a strong caution that the API cannot restore the course, which effectively warns against careless use. However, it never says when to prefer this over update_course or other course-management tools, so the guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.