Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Material de una lección

list_lesson_items
Read-only

Lists the quiz, self-assessment questions, flashcards, and games in a lesson with their IDs so you can edit or delete them.

Instructions

[Equipo del aula · solo lectura] Lista con sus IDs el quiz, las preguntas de autoevaluación, las tarjetas y los juegos de una lección, para poder editarlos o borrarlos.

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>",
      "session_id": "<session_id>"
    },
    "name": "list_lesson_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesLección
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the '[Equipo del aula]' scope tag, signalling this is a classroom-team surface, and confirms IDs are returned — useful context beyond the annotations. It does not cover ordering, pagination, or what happens for an empty lesson.

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?

A single sentence, front-loaded with the bracketed access-scope tag followed by verb and resource list. Every clause earns its place; only the redundant '[solo lectura]' duplicates the readOnlyHint annotation.

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?

With no output schema, the description carries the burden of saying what comes back, and it does: the four item types plus their IDs. Minor gaps remain around result ordering and whether items are grouped by type, but for a two-parameter read-only list tool it is largely sufficient.

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% and both parameters carry descriptions ('Lección', 'Aula') with UUID formats. The description adds no parameter-level detail beyond the schema, which is acceptable at full coverage — baseline 3.

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 opens with a specific verb ('Lista') and enumerates the exact resources returned: quiz, self-check questions, flashcards and games, scoped to a single lesson. That enumeration differentiates it from get_lesson and the save_/delete_ siblings, though it never names an alternative tool 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?

The trailing purpose clause 'para poder editarlos o borrarlos' implies the workflow: call this first to obtain IDs, then edit or delete. It gives context for when to use it, but there are no explicit exclusions and no sibling named (e.g. get_lesson vs list_lesson_items is left 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