Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crear o editar una pregunta de quiz

save_quiz_question

Create a quiz question in a lesson or edit an existing one by sending its question ID. Set the prompt, 2–6 options, the correct option, and optional difficulty, position, or explanation.

Instructions

[Equipo del aula] Crea una pregunta de quiz en una lección o edita una existente (envía question_id).

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

Input Schema

NameRequiredDescriptionDefault
promptYesPregunta
correctYesNúmero de la opción correcta, desde 1
optionsYesDe 2 a 6 opciones
positionNo
difficultyNo1 fácil, 5 difícil
session_idYesLección
explanationNoPor qué esa es la correcta
question_idNoPregunta a editar
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already supply readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's remaining job is to disclose edit semantics. It reveals that passing question_id switches to edit mode, which is genuine behavioral context, but it does not say whether an edit overwrites existing options/explanation or whether required fields must be resent, nor what permissions are needed.

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?

A single bracketed audience tag plus one sentence, with the create action front-loaded and the edit trigger appended as a parenthetical. Nothing is repeated from the title and no sentence is wasted.

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?

With nine parameters, five required, no output schema and no enums, this mutation tool needs a bit more than two clauses. The create/edit distinction is covered, but the description is silent on how save-exam, self-check and bulk-question siblings divide the territory, and on what a successful save returns or replaces.

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 89%, so the schema already explains prompt, options, correct, difficulty, explanation, session_id and classroom_id. The description only adds meaning for question_id (the edit trigger); the other eight parameters get nothing beyond structured fields, which is the expected baseline when coverage is high.

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 uses a specific verb ('Crea') plus resource ('pregunta de quiz') and states the scope (a lesson), and it distinguishes the create and edit modes by the question_id signal. It does not differentiate from close siblings such as add_quiz_questions or save_self_check_question, so an agent cannot tell from the text alone which of these writes a quiz question.

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 parenthetical '(envía question_id)' gives a clear rule for choosing edit mode over create mode, which is the most useful routing hint here. There is no guidance on when to use this single-question tool versus the bulk add_quiz_questions sibling, nor on any prerequisites such as the lesson needing to exist or permissions on the classroom.

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