Skip to main content
Glama

Contenido del Curso en EVA

eva_contenido_curso
Read-onlyIdempotent

Lists sections, modules, assignments, and resources for an EVA course, with optional type or section filters to control context size.

Instructions

Lista las secciones, módulos, tareas y recursos pertenecientes a un curso en EVA. Permite filtrar por tipo o sección para presupuestar contexto.

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": {
      "curso_id": "<curso_id>"
    },
    "name": "eva_contenido_curso"
  }
}

Input Schema

NameRequiredDescriptionDefault
curso_idYesID numérico del curso en EVA
seccion_idNoID numérico de la sección a consultar (opcional, omite para todas)
filtro_tipoNoFiltro opcional por tipo de recurso (ej: 'assign', 'resource', 'folder', 'url')
forzar_refrescoNoSi es true, invalida la caché en memoria y consulta directamente a EVA (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / forzar_refresco / default
      Removed value: -false
    • changedInput schema / properties / forzar_refresco / description
      Previous value: -"Si es true, invalida la caché en memoria y consulta directamente a EVA"New value: +"Si es true, invalida la caché en memoria y consulta directamente a EVA (por defecto: false)"
  2. Changed8 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / curso_id / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / curso_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / curso_id / minimum
      Added value: +1
    • addedInput schema / properties / seccion_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / seccion_id / minimum
      Added value: +-9007199254740991
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "cursoId": {
      -      "type": "number"
      -    },
      -    "secciones": {
      -      "type": "array"
      -    },
      -    "totalSecciones": {
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "cursoId",
      -    "secciones",
      -    "totalSecciones"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. First observedv1.0.6

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile needs no restating. The description adds a useful signal that the payload is large enough to warrant context budgeting, but says nothing about caching behavior beyond what the forzar_refresco schema field already documents, nor about response shape or depth.

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 tight sentences: the first front-loads what is returned, the second the filtering capability and its purpose. No filler, no repetition of the title.

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 a fully documented 4-parameter schema, rich annotations, and no output schema, the description covers what an agent needs to call it correctly. A brief note on whether results are hierarchical (sections containing modules) would close the remaining gap.

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 every parameter including the cache-invalidation flag is already documented. The description only echoes the tipo/sección filtering idea, which is the baseline expectation at full coverage.

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 ("Lista") and enumerates the resources returned (secciones, módulos, tareas y recursos) scoped to a single course, which cleanly separates it from eva_materias (course-level listing) and eva_tareas_y_notas. It does not explicitly name a sibling it replaces, so it lands at 4 rather than 5.

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?

"Permite filtrar por tipo o sección para presupuestar contexto" implies the usage pattern (narrow the call to reduce context cost) but never states when to prefer this over eva_buscar_materiales or eva_tareas_y_notas, nor any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.