Skip to main content
Glama
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cuestionarios y Exámenes Parciales en EVA

eva_cuestionarios
Read-onlyIdempotent

Check Moodle EVA questionnaire openings, closings, attempts, and grades for a course or active calendar items; supports read-only academic lookup.

Instructions

Consulta cuestionarios, exámenes parciales online, fechas de apertura/cierre, intentos y calificaciones en EVA Moodle (Lectura pura).

Input Schema

NameRequiredDescriptionDefault
curso_idNoID del curso en EVA. Si se omite, busca cuestionarios activos en el calendario y materias actuales.
forzar_refrescoNoSi es true, ignora la caché de 45-60 s y consulta de nuevo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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 / forzar_refresco
      Added value: +{
+  "default": false,
+  "description": "Si es true, ignora la caché de 45-60 s y consulta de nuevo",
+  "type": "boolean"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "cuestionarios": {
-      "type": "array"
-    }
-  },
-  "required": [
-    "cuestionarios"
-  ],
-  "type": "object"
-}New value: +null
  2. First observedv1.0.6

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint; "Lectura pura" merely restates the read-only hint rather than adding context. The mention of intentos and calificaciones does reveal what the response contains, but caching behavior (45–60 s) and the fallback scoping are only in the schema, so value beyond structured fields is modest.

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 no filler, and the read-only marker is placed at the end as a quick qualifier. Slightly dense field listing, but every element earns its place.

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 low-complexity, two-optional-parameter read tool with no output schema and full annotation coverage, the description is sufficient: it names the resource, the fields returned, and the read-only nature. It could be strengthened by noting the cache/fallback behavior, but the schema already carries that.

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 parameters (curso_id fallback behavior and forzar_refresco cache bypass) are fully documented in the schema. The description adds no parameter-level detail, which is acceptable at this coverage level but earns no extra credit.

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 ("Consulta") and concrete resources (cuestionarios, exámenes parciales online) plus the data returned (fechas de apertura/cierre, intentos, calificaciones), which clearly separates it from eva_tareas_y_notas or eva_foros. It does not name an alternative sibling explicitly, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description says what it retrieves but never states when to prefer it over neighbors like eva_tareas_y_notas or guarani_cronograma_evaluaciones, nor any precondition. The only situational hint (omitting curso_id falls back to active quizzes in the calendar) lives in the schema, not the description.

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