Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crear módulo

create_module

Adds an editable module to the end of a course, keeping it in draft by default and allowing immediate publication when needed.

Instructions

[Equipo del aula] Crea un módulo al final de un curso que puedes editar. Queda en borrador salvo que pidas publicarlo.

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>",
      "course_id": "<course_id>",
      "title": "<title>"
    },
    "name": "create_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNolecciones (lectura con quiz y juegos) o videolecciones
titleYesTítulo del módulo
lockedNoBloqueado hasta que se abra manualmente
publishNoPublicarlo de inmediato
opens_atNoFecha de apertura en ISO 8601
course_idYesCurso
objectiveNoQué se lleva quien lo termina
descriptionNoDescripción del módulo
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/safe profile is covered. The description adds real value beyond that: the module is appended at the end of the course, it is editable afterwards, and it stays in draft unless publication is explicitly requested — a non-obvious default that affects follow-up calls.

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 with zero filler; the placement constraint and the draft-by-default behavior are both front-loaded and immediately actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter creation tool with full schema coverage and no output schema, the description covers the essentials an agent needs: where the module lands and its initial publication state. It could go slightly further by noting what identifier is returned or how kind affects later content, but nothing critical is missing.

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%, so every parameter including kind, locked, opens_at and publish is already documented in the schema. The description's mention of publishing merely restates the publish parameter's default and adds no format, constraint, or interaction detail beyond the schema.

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 módulo') plus a placement detail ('al final de un curso'), which distinguishes it from create_lesson, create_course and import_module_content. It stops short of naming any sibling explicitly, so an agent must infer the boundary from the resource noun alone.

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 description implies usage context (creating a module inside an existing course) and clarifies the default draft state, but gives no explicit when-to-use vs. when-not guidance and never points to alternatives such as import_module_content for bulk content or create_lesson for adding items afterwards.

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