Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Avance del grupo

classroom_progress
Read-only

Summarizes each student's completed lessons, passed quizzes, points, and days since activity for a classroom, and can filter learners by inactivity.

Instructions

[Equipo del aula · solo lectura] Resume el avance de cada estudiante del aula: lecciones completadas, quizzes aprobados, puntos y días sin actividad. Puede filtrar a quienes llevan inactivos.

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

Input Schema

NameRequiredDescriptionDefault
limitNoCuántos estudiantes devolver (los más inactivos primero)
classroom_idYesAula
inactive_daysNoSolo quienes llevan al menos estos días sin actividad

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/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 useful context about what is summarized (lessons, quizzes, points, inactivity), but does not disclose ordering behavior, pagination, or authorization requirements beyond the annotations.

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?

The description is two sentences and front-loads the read-only classroom scope before the purpose and filter capability. It is efficient, though the bracketed tag partially repeats annotation information.

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 read-only summary tool with three well-documented parameters and no output schema, the description gives enough detail about the metrics returned and the inactive filter to call it correctly. It could be stronger by clarifying how this differs from per-student detail tools, but the core behavior is adequately covered.

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 three parameters are already documented in the schema. The description mentions inactive filtering, which maps to inactive_days, but adds no new syntax, format, or behavioral detail beyond the schema's own parameter descriptions.

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 states a specific verb ('Resume') and resource ('el avance de cada estudiante del aula') and lists the metrics returned: lessons completed, quizzes passed, points, and inactive days. This is clear enough to distinguish it from generic member listing, but it does not explicitly differentiate it from siblings like get_student_detail or list_members.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains a filtering capability ('Puede filtrar a quienes llevan inactivos') but gives no explicit guidance on when to use this tool versus alternatives such as get_student_detail for one student or list_members for roster data. Usage is only implied by the phrase 'avance de cada estudiante del aula'.

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