Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crear o editar una pregunta de examen

save_exam_question

Create a new exam question or update an existing one in a Chispa classroom exam by providing the prompt, answer options, and correct answer. Use it to build assessments one question at a time.

Instructions

[Equipo del aula] Crea una pregunta de examen o edita una existente (envía question_id). Para muchas preguntas usa add_exam_questions.

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>",
      "prompt": "<prompt>",
      "options": "<options>",
      "correct": "<correct>"
    },
    "name": "save_exam_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoTema
promptYesPregunta
correctYesNúmero de la opción correcta, desde 1
exam_idYesExamen
optionsYes
positionNo
session_idNoLección del módulo que conviene repasar
explanationNoExplicación
question_idNoPregunta a editar
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that this is an upsert whose mode is decided by presence of question_id, which is real behavioral context. It says nothing about whether an edit replaces all fields, what happens to position ordering, or whether edits are reversible.

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 short sentences front-load the operation and then the bulk alternative, with no filler. The bracketed team tag is the only arguably optional element.

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 ten-parameter mutation tool with no output schema, the description is thin: it never says whether an edit requires resending prompt/options/correct, how position interacts with existing questions, or what happens on a question_id that doesn't belong to the exam. Annotations cover safety, but call correctness is only partially supported.

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 80% and the question_id description already says 'Pregunta a editar', so the description's mention of question_id largely repeats structured data. None of the other nine parameters (position, session_id, topic, correct index bounds) get extra meaning from the description; 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 (create or edit an exam question) and explains that editing is triggered by sending question_id. It does not distinguish itself from the similarly named save_quiz_question or save_self_check_question siblings, leaving the agent to infer the scope from the name alone.

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?

Explicitly names the alternative add_exam_questions for creating many questions at once, which is genuine routing guidance. It gives no exclusion for other question types (quiz, self-check) and no prerequisites such as required permissions or that the exam must exist.

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