Skip to main content
Glama
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Contenido del Curso en EVA

eva_contenido_curso
Read-onlyIdempotent

Lists sections, modules, assignments, and resources for an EVA course, with optional filters by section or resource type to help control context size.

Instructions

Lista las secciones, módulos, tareas y recursos pertenecientes a un curso en EVA. Permite filtrar por tipo o sección para presupuestar contexto.

Input Schema

NameRequiredDescriptionDefault
curso_idYesID numérico del curso en EVA
seccion_idNoID numérico de la sección a consultar (opcional, omite para todas)
filtro_tipoNoFiltro opcional por tipo de recurso (ej: 'assign', 'resource', 'folder', 'url')
forzar_refrescoNoSi es true, invalida la caché en memoria y consulta directamente a EVA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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 / seccion_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / seccion_id / minimum
      Added value: +-9007199254740991
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "cursoId": {
-      "type": "number"
-    },
-    "secciones": {
-      "type": "array"
-    },
-    "totalSecciones": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "cursoId",
-    "secciones",
-    "totalSecciones"
-  ],
-  "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 only a vague nod to context budgeting ('presupuestar contexto'), but never mentions that results may be large, that caching exists (only surfaced in the schema via forzar_refresco), or anything about latency from hitting EVA directly.

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 compact sentences, front-loaded with what is returned and followed by the filtering capability. No redundant or filler text.

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 read-only listing tool with full schema coverage and no output schema, the description conveys enough about returned entities to call it confidently. It could say more about volume/ordering, but nothing essential is missing.

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 all four parameters, including the section filter and refresh-cache flag, are already documented. The description restates the type/section filtering already in the schema without adding format examples or interaction rules, 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 ('Lista') and enumerates the resource types returned (secciones, módulos, tareas, recursos) scoped to a course in EVA. It is clearly distinguishable from mutation tools, but it does not explicitly contrast itself with overlapping siblings like eva_tareas_y_notas or eva_buscar_materiales.

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 phrase 'para presupuestar contexto' implies this is the broad discovery tool used before narrower queries, but no explicit when-to-use/when-not-to-use or alternative routing is stated. An agent must infer that eva_tareas_y_notas or eva_buscar_materiales should be preferred for targeted lookups.

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