Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Detalle del curso

get_course
Read-only

Retrieves a course's editable details from a Chispa classroom—title, description, level, visibility, collection, and publication status—for read-only review.

Instructions

[Equipo del aula · solo lectura] Devuelve los datos editables de un curso del aula: títulos, descripción, nivel, visibilidad, colección y publicación.

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

Input Schema

NameRequiredDescriptionDefault
course_idYesCurso
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 structurally. The description reinforces scope ("Equipo del aula · solo lectura") but adds nothing about what happens when the course is missing, what access is needed, or whether unpublished content is included; "datos editables" for a read-only tool is also slightly ambiguous phrasing.

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 front-loaded sentence with a bracketed scope tag; nothing is wasted. "Datos editables" is the only slightly imprecise phrase for a read-only operation.

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 two-parameter read getter with full schema coverage and annotations covering safety, the description is nearly sufficient, and enumerating the returned fields compensates for the absent output schema. It could still clarify whether the response includes nested content such as modules or lessons.

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 coverage is 100% with both classroom_id and course_id documented, so the baseline is 3. The description adds no meaning about the identifiers beyond the schema, though the pairing of course and classroom context is implied.

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+resource ("Devuelve los datos editables de un curso del aula") and enumerates the fields returned (títulos, descripción, nivel, visibilidad, colección, publicación). It is distinguishable from list_courses, but it does not explicitly contrast itself with get_course_outline, which is the closest sibling.

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 "[Equipo del aula · solo lectura]" tag and "datos editables" strongly imply this is the read step before update_course, but the description never says when to use it instead of get_course_outline or list_courses. Usage is inferable rather than stated.

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