Skip to main content
Glama
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Materias y Cursos en EVA

eva_materias
Read-onlyIdempotent

List EVA Moodle virtual classrooms and enrolled subjects with course IDs, including active courses by default and archived or hidden courses on request.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. 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 readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the important default-filter behavior (archived courses omitted unless requested), but this largely restates the incluir_archivadas schema description, and it omits any note about caching, which the schema surfaces via forzar_refresco.

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, front-loaded with the core purpose, followed by the default-vs-opt-in distinction. There is no filler or repetition beyond the necessary clarification of default scope.

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-optional-boolean, read-only listing tool with no output schema, this is nearly sufficient: it conveys the resource enumerated and that results carry course identifiers. A brief note on return shape (names plus IDs, one entry per enrolled course) 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 both booleans are already documented, and the description's mention of incluir_archivadas adds no new semantics. forzar_refresco and its cache-invalidation contract are not addressed at all in the description, so it stays at the baseline.

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: 'Lista las aulas virtuales y materias matriculadas en EVA Moodle con sus identificadores de curso'. It is clearly a course-enumeration tool, distinct from content-level siblings like eva_contenido_curso or eva_tareas_y_notas. It does not explicitly name a sibling or position itself as the entry point that produces the course IDs other tools need.

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?

Explains the default behavior (active courses only) and the opt-in for archived/hidden courses, which implicitly tells the agent when to set the flag. However, it names no alternative tool and gives no explicit 'use this before X' guidance, despite being the natural discovery step for the eva_* family.

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