Skip to main content
Glama

Cronograma, Programa y Fechas de Parciales en EVA

eva_cronograma
Read-onlyIdempotent

Finds a subject's EVA schedule or program and extracts exam, retake, and assignment dates; if ambiguous, returns matching candidates, and reports when no schedule or dates are published.

Instructions

Busca el archivo de cronograma o programa de una materia en EVA y extrae las fechas de parciales, recuperatorios y entregas. Elige el programa/cronograma por nombre; si no hay uno claro devuelve candidatos para elegir. Incluye fechasDetectadas y avisoFechas (avisa si el documento no publica fechas concretas). Si no existe cronograma ni programa en el aula virtual, informa explícitamente que no hay.

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": {
      "materia": "<materia>"
    },
    "name": "eva_cronograma"
  }
}

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.7/5.0
Behavior4/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 is covered. The description adds genuine behavioral context beyond that: ambiguous-match handling that returns candidates, the fechasDetectadas and avisoFechas fields, and explicit reporting when no document exists.

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?

Four short sentences, front-loaded with the core action and followed by edge-case behavior. Each sentence carries information; only the closing clause slightly restates the cronograma/programa pairing already established earlier.

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 no output schema, the description compensates by naming the key return fields and the failure/ambiguity paths, which is what an agent needs to interpret results. The one gap is that it does not clarify its boundary against guarani_cronograma_evaluaciones or other EVA file tools.

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% and the single materia parameter is fully documented with type, length bounds and examples. The description only implies that the materia argument drives the search, adding no format or disambiguation detail beyond the schema, so baseline 3 applies.

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: locate the cronograma/programa file for a subject in EVA and extract exam/retake/delivery dates. That is far more than a restatement of the name. However, it never distinguishes itself from related siblings such as eva_buscar_materiales, eva_contenido_curso or especially guarani_cronograma_evaluaciones, which an agent could easily confuse it with.

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?

The description explains internal fallback behavior (pick by name, else return candidates) and the no-file case, which implies usage. But it gives no explicit when-to-use/when-not guidance and names no alternative tool, so the agent must infer that this is for EVA-hosted documents rather than Guaraní evaluation data.

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