Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crear curso

create_course

Create a draft course in a classroom, defaulting to classroom-only visibility and linking it when the caller administers that classroom. Confirm before publishing or making it public.

Instructions

[Equipo del aula] Crea un curso. Queda en borrador y con visibilidad «aula» salvo que se indique otra cosa. Solo si quien llama administra el aula, el curso queda vinculado a ella (igual que en la plataforma); si no, queda sin vincular. Confirma con la persona antes de publicar o hacerlo público.

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

Input Schema

NameRequiredDescriptionDefault
titleYesTítulo del curso
publishNoPublicarlo de inmediato
audienceNoA quién va dirigido
subtitleNoSubtítulo
objectiveNoObjetivo
difficultyNoNivel; omítelo para no mostrar nivel
visibilityNopublico (gratis), publico_pago o aula (solo el aula)aula
descriptionNoDescripción
classroom_idYesAula
collection_idNoColección propia

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?

Annotations only declare it is a non-read-only, non-destructive, closed-world write. The description adds real behavior: default draft state, default visibility, permission-dependent classroom linking (and what happens when the caller is not an admin), plus a confirmation requirement before publishing. It does not say what is returned or how to reference the created course afterwards.

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?

Four short sentences, front-loaded with the action and its default outcome, then the permission nuance and the confirmation rule. No filler, though the confirmation sentence is a policy statement rather than tool behavior.

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 10-parameter mutation with no output schema, the description covers the non-obvious parts: default draft/visibility state and the conditional classroom linkage. The remaining gap is what the call returns and how collection_id interacts with the created course.

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%, so every parameter including the publish and visibility enums is already documented in the schema. The description restates the default visibility and warns about publish, which is useful but adds little meaning beyond the structured fields; collection_id and difficulty are untouched.

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 curso") and immediately qualifies the resulting state (draft, visibility «aula»). It does not explicitly distinguish itself from siblings like update_course or activate_trial_course, but the create semantics are 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 conditions: created as draft unless otherwise indicated, linked to the classroom only if the caller administers it, and an explicit instruction to confirm with the person before publishing or making it public. No named alternative tool, so it stops short of full routing guidance.

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