Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crear escenario

create_scenario

Creates an editable open-ended scenario for the end of a course module and saves it as a draft; add the rubric separately with add_scenario_criteria.

Instructions

[Equipo del aula] Crea un caso práctico de respuesta abierta al final de un módulo de un curso que puedes editar. Queda en borrador; añade su rúbrica con add_scenario_criteria.

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>",
      "situation": "<situation>",
      "model_answer": "<model_answer>"
    },
    "name": "create_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTítulo
questionNoQué se pide concretamente
min_charsNoMínimo de caracteres de la respuesta
module_idYesMódulo
situationYesSituación que se debe resolver
repeatableNoSi se puede repetir cada cierto tiempo
repeat_daysNoDías entre intentos si es repetible
classroom_idYesAula
max_attemptsNoMáximo de intentos si es repetible
model_answerYesRespuesta de referencia
pass_percentNoPorcentaje para aprobar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, closed-world write. The description adds genuinely new behavioral information: the created object is left in draft state and needs a rubric before being usable, and it points to the next tool in the workflow. It omits what publishing requires (set_published) and what the call returns.

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 actor and action, then the initial state and the recommended follow-up. No filler; the bracketed team marker is a minor cost.

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?

Covers what is created, its draft state, and the rubric follow-up, which is the essential workflow context for an 11-parameter creation tool. It does not mention that the new scenario's identifier is needed for add_scenario_criteria, and with no output schema the agent gets no hint about the response.

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%, with every one of the 11 properties documented (title, situation, model_answer, min_chars, repeatable, repeat_days, max_attempts, pass_percent, ids). The description adds no parameter-level meaning, so the baseline of 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 concrete verb plus resource: creates an open-response practical scenario anchored at the end of a course module. This is clearly distinct from get_scenario/update_scenario/delete_scenario siblings, though it does not name any of them explicitly.

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?

Implies the correct usage sequence by saying the scenario stays in draft and that the rubric should be added with add_scenario_criteria. It gives no guidance on when to choose this versus update_scenario, nor on prerequisites such as the required module/classroom context.

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