Skip to main content
Glama
Sign In
UCA MCP

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Tareas y Notas en EVA

eva_tareas_y_notas
Read-onlyIdempotent

Retrieves tasks, deadlines, and submission statuses from EVA courses to help you track pending assignments and due dates across subjects.

Instructions

Obtiene tareas, plazos de entrega, estado de entregas y fechas límite en EVA.

Input Schema

NameRequiredDescriptionDefault
curso_idNoID del curso (opcional, omite para todas las materias)
incluir_cerradasNoSi es true, incluye tareas vencidas (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / incluir_cerradas / default
      Removed value: -false
    • changedInput schema / properties / incluir_cerradas / description
      Previous value: -"Si es true, incluye tareas vencidas"New value: +"Si es true, incluye tareas vencidas (por defecto: false)"
  2. 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": {
-    "tareas": {
-      "type": "array"
-    },
-    "total": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "tareas",
-    "total"
-  ],
-  "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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered without the description. The text adds only the set of fields returned; it says nothing about scoping semantics, how overdue vs. upcoming items are treated, or result volume/pagination. No contradiction with annotations.

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?

One front-loaded sentence with no filler. Slight redundancy between "plazos de entrega" and "fechas límite", which convey nearly the same thing, keeps it from a 5.

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?

With no output schema, the description should sketch the return shape (e.g., tasks grouped by course, submission status fields) so the agent can plan around it; that is missing. For a two-parameter read tool with full annotations the remaining gap is modest but real.

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 curso_id (omit for all subjects) and incluir_cerradas (default false) are fully documented in the schema. The description adds no extra meaning to either parameter, 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 specific verb ("Obtiene") and enumerates the resources it returns: tareas, plazos de entrega, estado de entregas y fechas límite en EVA. Clear enough to know what it does, but it never distinguishes itself from overlapping siblings like eva_entregas_proximas or eva_cronograma.

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 indication of when to pick this tool over eva_entregas_proximas (which also surfaces upcoming deadlines) or eva_cuestionarios (assessment-type tasks). No exclusions, prerequisites, or context of use are given.

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