Skip to main content
Glama

Materias y Cursos en EVA

eva_materias
Read-onlyIdempotent

Lists UCA EVA virtual classrooms and enrolled subjects with course IDs, including archived or hidden courses when requested.

Instructions

Lista las aulas virtuales y materias matriculadas en EVA con sus identificadores de curso. Por defecto lista cursos activos; con incluir_archivadas: true lista también los cursos pasados u ocultos.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "eva_materias"
  }
}

Input Schema

NameRequiredDescriptionDefault
forzar_refrescoNoSi es true, invalida la caché en memoria y consulta directamente a EVA (por defecto: false)
incluir_archivadasNoSi es true, incluye también los cursos ocultados o de semestres anteriores (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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)"
    • removedInput schema / properties / incluir_archivadas / default
      Removed value: -false
    • changedInput schema / properties / incluir_archivadas / description
      Previous value: -"Si es true, incluye también los cursos ocultados o de semestres anteriores"New value: +"Si es true, incluye también los cursos ocultados o de semestres anteriores (por defecto: false)"
  2. Changed3 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "materias": {
      -      "type": "array"
      -    },
      -    "total": {
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "materias",
      -    "total"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. First observedv1.0.6

TDQS

A4/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 meaningful scope behavior (active by default, archived hidden unless flagged), but omits that a prior uca_iniciar_sesion is required and says nothing about in-memory caching or result size.

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 sentences, zero filler, with the default listing behavior front-loaded ahead of the archive toggle.

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 zero-required-parameter read tool with full schema coverage and complete annotations, this is close to sufficient; it even notes that course identifiers come back. Only the shape of the returned course entries and the login precondition are left unstated, and there is no output schema to cover them.

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 booleans self-documented, so the baseline is 3. The description restates incluir_archivadas (adding only the 'past or hidden' nuance) and says nothing about forzar_refresco, leaving that entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: lists virtual classrooms/enrolled subjects in EVA with their course identifiers. That clearly separates it from sibling content tools like eva_contenido_curso or eva_tareas_y_notas, which operate on a single course once its id is known.

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

Usage Guidelines4/5

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

Explains the default behavior (active courses) and the exact condition for widening scope with incluir_archivadas: true, which is real usage guidance. It stops short of naming alternatives or stating that this is the entry point before other eva_ tools, so no explicit exclusions.

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