Skip to main content
Glama
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cronograma, Programa y Fechas de Parciales en EVA

eva_cronograma
Read-onlyIdempotent

Extracts exam, makeup, and assignment dates from a course's EVA Moodle schedule or program, and explicitly reports when no schedule or program exists.

Instructions

Busca el archivo de cronograma o programa de una materia en EVA Moodle y extrae las fechas de parciales, recuperatorios y entregas. Si no existe cronograma ni programa en el aula virtual, informa explícitamente que no hay.

Input Schema

NameRequiredDescriptionDefault
materiaYesNombre o código de la materia (ej: 'Álgebra', 'Física III', 'Ingeniería de Software')

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": {
-    "archivo": {},
-    "cursoId": {
-      "type": "number"
-    },
-    "encontrado": {
-      "type": "boolean"
-    },
-    "evaluacionesAula": {
-      "type": "array"
-    },
-    "lineasEvaluacion": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "materia": {
-      "type": "string"
-    },
-    "mensaje": {
-      "type": "string"
-    },
-    "textoCronograma": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "encontrado",
-    "mensaje"
-  ],
-  "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 readOnly, idempotent and openWorld, so the safety profile is covered. The description adds one useful behavioral trait—explicitly reporting when no cronograma/programa exists instead of failing silently—but says nothing about extraction limits, file formats handled, or what the returned date list looks like.

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 waste: the first front-loads what is searched and what is extracted, the second covers the no-result path. Nothing is redundant with the schema or annotations.

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 one-parameter read tool with no output schema, the description covers purpose, extracted data types and the empty-result behavior, which is nearly everything needed. The remaining gap is not routing the agent away from the Guarani-based sibling tool.

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% and the single `materia` parameter is fully documented with examples, so the description need not repeat it; it only references 'una materia' generically. Baseline 3 is appropriate since the schema does all the work.

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+resource: searches the syllabus/program file of a course in EVA Moodle and extracts exam, retake and assignment dates. The 'en EVA Moodle' scoping distinguishes it from guarani_cronograma_evaluaciones, but the sibling is never named, so the agent must infer the split itself.

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?

Usage is implied by the description (find evaluation dates inside the virtual classroom), and the no-result case is explicitly handled. However, there is no guidance on when to prefer this over guarani_cronograma_evaluaciones or eva_buscar_materiales, which overlap in intent.

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