Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Borrar módulo

delete_module
Destructive

Permanently deletes a classroom module along with its lessons and assessments. Requires explicit confirmation because the action is irreversible.

Instructions

[Equipo del aula · irreversible] Borra definitivamente un módulo con sus lecciones y evaluaciones. 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>",
      "module_id": "<module_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_module"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds material context beyond them: the deletion cascades to lessons and evaluations, it cannot be undone, and human confirmation is mandatory. The bracketed "Equipo del aula" scope hint is left unexplained, which keeps this from a full 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?

Two tight sentences with no filler, and the irreversible/cascade warning is front-loaded where an agent will read it first. The leading bracketed tag is slightly cryptic but does not waste meaningful space.

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 three-parameter destructive tool with no output schema, the definition covers the essentials: what is removed, that it is irreversible, and that confirmation is required. Missing are failure behavior and permission prerequisites implied by the vague "Equipo del aula" tag.

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 100% and the `confirm` field already documents the boolean-const requirement in detail, so the schema carries the parameter burden. The description reinforces the confirmation concept but adds no syntax or semantics for `classroom_id` or `module_id` beyond what the schema states.

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?

"Borra definitivamente un módulo con sus lecciones y evaluaciones" gives a specific verb plus resource plus cascade scope, so an agent can distinguish it from delete_lesson or delete_course by the resource targeted. It stops short of naming an alternative sibling or contrasting with non-destructive options like set_published, so it is clear but not fully differentiated.

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?

The description imposes one real usage rule — obtain explicit confirmation from the person before calling, reinforced by the `confirm` parameter. It does not say when deletion is the right choice versus unpublishing or archiving, nor which sibling to reach for instead, so the when-to-use guidance is only implied by the verb.

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