Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Borrar pregunta de examen

delete_exam_question
Destructive

Permanently deletes a question from an exam in a Chispa classroom; use classroom_id and question_id to remove an unwanted exam question.

Instructions

[Equipo del aula · irreversible] Borra una pregunta de un examen.

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>",
      "question_id": "<question_id>"
    },
    "name": "delete_exam_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
question_idYesPregunta
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description reinforces this with 'irreversible' and adds the scope qualifier 'Equipo del aula' (classroom team), implying a permission/ownership context the annotations do not express. It says nothing about side effects on question ordering, exam state, or whether the exam must be unpublished.

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?

One compact sentence with the critical attribute (irreversibility) and scope front-loaded in a bracket tag. There is little waste, though some of the bracket content duplicates the destructiveHint annotation.

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 two-parameter destructive tool with full schema coverage, annotations and no output schema, the description is minimum viable. It omits what the caller gets back, what happens to sibling questions' positions, and any precondition such as exam publication state, which matters for a destructive operation.

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 both UUID parameters are documented in the schema, so the schema carries the param burden. The description adds no meaning beyond it — it does not clarify that classroom_id scopes the ownership check while question_id identifies the item to remove. 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?

The description names a specific verb and resource ('Borra una pregunta de un examen'), so an agent immediately knows it removes a single exam question. It does not explicitly contrast with siblings such as delete_quiz_question or delete_self_check_question, but the resource word 'examen' does the disambiguation well enough.

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

Usage Guidelines2/5

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

There is no guidance on when to use this rather than save_exam_question, delete_exam, or the quiz/self-check deletion variants, and no preconditions are stated. The only hint is the bracketed scope tag, which is not actionable usage guidance.

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