Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Asociar temas a un material

set_item_themes

Assign or replace the course themes linked to classroom lessons, quiz or exam questions, cards, games, or scenarios.

Instructions

[Equipo del aula] Fija a qué temas del curso pertenece una lección, pregunta de quiz o de examen, tarjeta, juego o escenario. Reemplaza las asociaciones previas.

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>",
      "kind": "<kind>",
      "item_id": "<item_id>",
      "theme_ids": "<theme_ids>"
    },
    "name": "set_item_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYessesion (lección), pregunta_quiz, pregunta_examen, tarjeta, juego o escenario
item_idYesMaterial
theme_idsYesLista vacía para quitar todos los temas
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, so the mutation nature is known, but the description adds a genuinely important behavioral fact beyond them: previous associations are fully replaced, not merged. That is exactly the kind of side-effect disclosure annotations do not provide. It stops short of noting the empty-list-removes-all case or any permission requirements.

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 sentences with zero waste: the scope tag and the set-of-item-kinds come first, and the replacement caveat follows immediately. Nothing is repeated from the schema and nothing could be cut without losing meaning.

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 four-required-parameter mutation with full schema coverage and no output schema, the description covers purpose, target item kinds, and the overwrite semantics. It leaves minor gaps: whether the item and themes must already exist, and what the tool returns, but these are small relative to the schema's completeness.

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 all four parameters are already documented, including the enum values and the 'Lista vacía para quitar todos los temas' note on theme_ids. The description adds no format, ordering, or limit details beyond the schema, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (fija) and resource (temas del curso asociados a un material) and enumerates the exact item kinds matching the `kind` enum: lección, pregunta de quiz/examen, tarjeta, juego, escenario. This clearly separates it from siblings like save_theme, list_course_themes, and save_quiz_question, which create themes or items rather than associate them.

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 implied by the enumerated item kinds and the '[Equipo del aula]' context tag, and the replacement clause hints at the when-to-use case (re-association rather than incremental add). There is no explicit exclusion or pointer to alternatives such as creating themes first with save_theme, so an agent must infer the workflow.

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