Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Índice del curso

get_course_outline
Read-only

Retrieves a course's modules and lessons with their publication status from a Chispa classroom, helping you review course structure and visibility.

Instructions

[Equipo del aula · solo lectura] Devuelve los módulos y lecciones de un curso del aula, con su estado de 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_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYesCurso
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/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 and 'solo lectura' in the description is largely redundant. The description does add that results include publication status of modules and lessons, which is real behavioral context, but says nothing about ordering, depth, lesson item inclusion, or size of the response.

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 the scope tag first and the resource second; nothing extraneous. The only waste is 'solo lectura', which repeats the readOnlyHint annotation.

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

Completeness3/5

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

There is no output schema, so the description bears the burden of describing the return value, and it only says 'modules and lessons with publication state' — no indication of nesting, ordering, or whether lesson items are included. Adequate to invoke the tool, but thin for a structure-listing read with no output contract.

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% with the two required UUIDs ('Curso' and 'Aula') documented in the schema. The description adds no meaning beyond that — no note on whether classroom_id is required to scope access, or on UUID format expectations — so the baseline 3 applies.

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: returns the modules and lessons of a classroom course, plus their publication state. That clearly separates it from get_course (course metadata) and get_module (single module), but it never names those siblings explicitly, so the differentiation is inferable rather than stated.

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 gives context about who uses it and that it is a read, implying you call it to inspect a course's structure. There is no explicit when-to-use or when-not-to-use guidance against the many neighboring tools (get_module, list_lesson_items, list_course_themes), leaving the agent to infer boundaries.

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