Skip to main content
Glama
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Entregas Próximas y Avisos de la Semana en EVA

eva_entregas_proximas
Read-onlyIdempotent

Lists upcoming assignments, practical works, and activities due within a specified number of days (default 7), plus recent course notices, optionally filtered by course.

Instructions

Consulta qué tareas, trabajos prácticos o actividades tienen fecha de vencimiento en los próximos días (por defecto 7 días / la semana que viene) y avisos recientes de cátedra.

Input Schema

NameRequiredDescriptionDefault
diasNoCantidad de días a futuro (por defecto 7 para la próxima semana)
curso_idNoID de curso en EVA opcional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "avisosRecientes": {
-      "type": "array"
-    },
-    "entregas": {
-      "type": "array"
-    },
-    "mensaje": {
-      "type": "string"
-    },
-    "totalPendientes": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "totalPendientes",
-    "entregas",
-    "mensaje"
-  ],
-  "type": "object"
-}New value: +null
  2. First observedv1.0.6

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the result mixes two kinds of data (deadlines plus 'avisos recientes de cátedra'), which is useful, but it says nothing about ordering, grouping, or how the 30-day cap behaves — that lives only in the schema.

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 that names the resource and the default horizon before any caveats. The nested parenthetical '(por defecto 7 días / la semana que viene)' is slightly redundant with the schema default but not wasteful.

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?

No output schema exists, and the tool returns two distinct payload types (due items and notices), yet the description does not say how they are returned or whether either section can be empty. Annotations carry the safety story, but the return-shape gap leaves it only minimally complete.

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 are already documented and the baseline is 3. The description only restates the default window; it adds no guidance on how curso_id scopes the results or what happens when it is omitted.

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 two concrete resources: items with upcoming due dates and recent course notices. An agent can tell it apart from eva_tareas_y_notas or eva_cronograma by the 'próximos días' framing, but the description never names those siblings to make the boundary explicit.

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 parenthetical '(por defecto 7 días / la semana que viene)' implies the typical use case — a weekly look-ahead — but there is no explicit statement of when to prefer this over eva_tareas_y_notas, eva_cronograma, or uca_resumen_semanal, nor any exclusion.

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