Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Borrar curso

delete_course
Destructive

Permanently deletes a course, including its modules, lessons, and assessments, after explicit confirmation and only for the course creator.

Instructions

[Equipo del aula · irreversible] Borra definitivamente un curso con todos sus módulos, lecciones y evaluaciones. Solo quien lo creó. Irreversible: pide confirmación explícita a la persona.

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": {
      "classroom_id": "<classroom_id>",
      "course_id": "<course_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesDebe ser true: la persona confirmó esta acción irreversible
course_idYesCurso
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds what those hints cannot: the deletion is irreversible, it cascades to every nested module, lesson and assessment, and it is restricted to the course creator. The instruction to obtain explicit confirmation from the person is concrete operational behavior.

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 tight sentences with a bracketed tag front-loading team scope and irreversibility. Every clause carries distinct information: scope of cascade, permission, and confirmation requirement.

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

Completeness5/5

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

For a destructive, no-output-schema, three-parameter tool this covers the essentials: what is destroyed, who may do it, and that a human must confirm. Nothing an agent needs before invoking it is missing.

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 coverage is 100% and each parameter already carries a description, including confirm's const-true constraint and the person-confirmed framing. The description reinforces the confirmation requirement but adds no identifier format or lookup detail beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Borra definitivamente') and resource ('un curso') plus the exact cascade scope: all modules, lessons and assessments. That scope is what separates it from the many delete_module / delete_lesson / delete_exam siblings, so an agent can pick it without opening any 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 clear preconditions for use: only the creator may call it and an explicit human confirmation is required first. It does not explicitly name the narrower alternatives (e.g. delete_module) as the fallback when only part of the course should go, so guidance is strong but not complete routing.

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

Deploy Server

Other Tools