Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ordenar los cursos de una colección

reorder_collection_courses

Sets the order of all courses in a teacher's collection; provide a complete ordered list of course IDs so the collection displays in that sequence.

Instructions

[Cuenta docente] Fija el orden de los cursos de una colección tuya. La lista debe incluir todos sus cursos.

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": {
      "collection_id": "<collection_id>",
      "course_ids": "<course_ids>"
    },
    "name": "reorder_collection_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idsYes
collection_idYesColección

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation/safety profile is covered structurally. The description adds real value by implying this is a full-replacement reordering (the list must contain all courses), but it does not say what happens when the list is incomplete or contains foreign courses — a key behavioral detail for a set-ordering operation.

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 plus a bracketed scope tag; the account requirement, the action and the completeness constraint are all front-loaded with zero filler.

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

Completeness5/5

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

For a two-parameter mutation with no output schema and annotations covering safety, the description supplies the account prerequisite, the full-replacement semantics and the ordering meaning. Nothing an agent needs in order to invoke it correctly is missing.

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 50% and the schema labels are terse ("Colección", "Curso"), so the description carries weight. It clarifies that course_ids is the complete membership of the collection and that array order equals display order, which is the essential semantic the schema alone does 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?

States a specific verb and resource ("Fija el orden de los cursos de una colección") and scopes it with "tuya", so the agent knows it acts on the caller's own collection. It is distinguishable from generic course tools like create_course or move_course_to_collection, though it does not name a sibling alternative 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?

"[Cuenta docente]" signals a teacher-account precondition and "La lista debe incluir todos sus cursos" gives a hard usage constraint, which is genuinely useful. However, it never contrasts with move_course_to_collection or explains when reordering is needed versus moving courses in/out, leaving the choice between collection tools to inference.

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