Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Borrar examen

delete_exam
Destructive

Permanently deletes an exam and all its questions and attempts after explicit confirmation. Use for irreversible removal of an exam from a classroom.

Instructions

[Equipo del aula · irreversible] Borra definitivamente un examen con sus preguntas e intentos. 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>",
      "exam_id": "<exam_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_exam"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the danger profile is known. The description still adds real value by disclosing the cascade ('con sus preguntas e intentos') and the confirmation ritual, but it says nothing about failure behavior, whether the classroom must be published, or permission requirements.

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 short sentences, front-loaded with the scope tag and the destructive verb, with zero filler. Minor redundancy: 'irreversible' appears twice and the confirmation instruction restates the 'confirm' parameter.

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 full annotation coverage and no output schema, the description covers the essentials: what it removes, that it cascades, and that it cannot be undone. Only permission and failure-mode details are missing, which is minor at this complexity.

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 all three parameters carry descriptions, including the 'confirm' const constraint. The description does not add meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Borra definitivamente un examen') and scopes the blast radius ('con sus preguntas e intentos'), which implicitly separates it from delete_exam_question and delete_quiz_question. No sibling is named explicitly, so it stops just short of full differentiation.

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 a concrete precondition: ask the person for explicit confirmation before invoking, and the bracketed tag 'Equipo del aula' signals the required scope. It does not name alternatives (e.g. update_exam) or say when deletion is inappropriate, so it is clear context without exclusions.

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