Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ordenar lecciones

reorder_lessons

Set the lesson order for a module by providing every lesson ID in the desired sequence.

Instructions

[Equipo del aula] Fija el orden de las lecciones de un módulo. La lista debe incluir todas las lecciones del módulo, en el orden deseado.

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>",
      "session_ids": "<session_ids>"
    },
    "name": "reorder_lessons"
  }
}

Input Schema

NameRequiredDescriptionDefault
module_idYesMódulo
session_idsYes
classroom_idYesAula

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 already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), but they do not reveal that this is a full-replacement operation. The description adds exactly that critical contract — the list must contain every lesson of the module — plus the '[Equipo del aula]' scope marker indicating the classroom-team permission context. It does not state what happens if the list is incomplete or whether the call is idempotent.

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: the action first, then the hard constraint on the payload. Nothing is padded, repeated, or buried.

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 three-required-parameter mutation with no output schema, the description covers scope, permission domain, and the key payload invariant. Remaining gaps are outcome-related (behavior on a partial or invalid list, what is returned), which are secondary but not trivial for a full-overwrite reorder.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, but the inline schema labels are mere nouns ('Módulo', 'Lección', 'Aula'), so coverage overstates the value delivered. The description meaningfully specifies the semantics of session_ids as an ordered, exhaustive list of the module's lessons, which the schema's type/minItems/maxItems constraints alone do not convey.

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 names a specific verb+resource: 'Fija el orden de las lecciones de un módulo' (sets the order of a module's lessons). The module-scoped resource also implicitly separates it from the sibling reorder_modules, though that sibling is never named 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?

Usage is only implied: the caller learns the list must be the complete, ordered set of the module's lessons, which tells you when this tool is the right one. There is no explicit when-not guidance, no mention of prerequisites (e.g. needing the module's current lessons first), and no reference to the alternative reorder_modules or update_lesson.

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