Skip to main content
Glama

Cuestionarios y Exámenes Parciales en EVA

eva_cuestionarios
Read-onlyIdempotent

Query EVA quizzes, online midterm exam dates, attempts, and grades by course ID to check availability and results without manual navigation.

Instructions

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

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_cuestionarios"
  }
}

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 (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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, ignora la caché de 45-60 s y consulta de nuevo"New value: +"Si es true, ignora la caché de 45-60 s y consulta de nuevo (por defecto: false)"
  2. 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
  3. 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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered and '(Lectura pura)' merely restates it. The description does add value by enumerating what the response contains (apertura/cierre dates, attempts, grades), which matters since there is no output schema, but it says nothing about the 45–60s cache, auth needs, or pagination.

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 the resource first and the read-only qualifier last; no filler. It is dense and efficient, though the parenthetical is the weakest part since it duplicates annotation data.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read tool with full schema coverage and no output schema, the description adequately conveys purpose and return contents. It falls short on routing: with both EVA and Guaraní evaluation tools in the sibling set, an agent gets no signal about which to choose.

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 both parameters are well documented there, including the meaningful omission behavior for curso_id and the cache bypass for forzar_refresco. The description adds no parameter detail of its own, so the 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 concrete verb ('Consulta') and specific resources (cuestionarios, exámenes parciales) plus the data returned (fechas de apertura/cierre, intentos, calificaciones), scoped to EVA. It doesn't name a sibling to distinguish from — notably guarani_cronograma_evaluaciones, which covers exam dates from a different system — so the EVA/Guaraní boundary is only implied.

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?

No when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. '(Lectura pura)' signals a read-only operation but not a selection criterion. The key usage fact — that omitting curso_id sweeps the calendar and current subjects — lives only in the schema, not in the description.

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