Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crear simulacro o examen

create_exam

Creates an editable draft exam at the end of a course module for a classroom, letting teachers define attempts, timing, and pass criteria. Add questions afterwards; the exam stays in draft.

Instructions

[Equipo del aula] Crea un simulacro o examen al final de un módulo de un curso que puedes editar. Queda en borrador; añade preguntas con 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>",
      "module_id": "<module_id>",
      "title": "<title>"
    },
    "name": "create_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTítulo
module_idYesMódulo
repeatableNoSi se puede repetir cada cierto tiempo
descriptionNoInstrucciones
repeat_daysNoDías entre intentos si es repetible
review_modeNoQué ve el estudiante al terminarexplicaciones
classroom_idYesAula
max_attemptsNoMáximo de intentos si es repetible
pass_percentNoPorcentaje para aprobar
time_limit_minutesNoTiempo límite en minutos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the exam is created as a draft ('Queda en borrador') and is editable, and flags a required team/classroom context. It does not mention that publishing likely requires a separate step (set_published), which is the main behavioral gap for a mutation tool with destructiveHint=false.

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: first the action and placement, then the resulting state and next step. No filler, and the most decision-relevant information is front-loaded.

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 10-parameter mutation tool with no output schema, the description covers purpose, draft state and the next call, but never says what is returned (e.g. the new exam's id needed for add_exam_questions) or how the exam becomes visible to students. Those omissions matter given the absence of an output schema.

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 100%, with defaults, ranges and an enum all documented, so the schema carries the parameter semantics. The description adds nothing about the behavioral parameters (repeatable, repeat_days, max_attempts, time_limit_minutes, pass_percent), so 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 ('Crea un simulacro o examen') plus placement ('al final de un módulo de un curso'), which separates it from import_exam and update_exam. It does not explicitly name those siblings, but the creation framing is unambiguous.

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 clear context for use (at the end of a course module) and names the follow-up tool ('añade preguntas con add_exam_questions'), which routes the agent correctly. It does not state when to prefer import_exam instead or what permissions the '[Equipo del aula]' scope requires.

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