Skip to main content
Glama
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Plan Óptimo de Cursada y Desbloqueo de Correlatividades

guarani_plan_optimo
Read-onlyIdempotent

Ranks available courses by how many subsequent subjects they unlock and computes the critical-path height plus minimum semesters needed to graduate, helping plan the next term.

Instructions

Rankea las materias habilitadas para cursar según su impacto multiplicador en el grafo de correlatividades (cierre transitivo de materias desbloqueadas) y calcula la altura del camino crítico y la estimación de cuatrimestres mínimos para recibirse.

Input Schema

NameRequiredDescriptionDefault
carreraNoNombre o código de la carrera
max_sugerenciasNoCantidad máxima de materias a sugerir prioritariamente para el próximo cuatrimestre (por defecto 5)

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": {
-    "carrera": {
-      "type": "string"
-    },
-    "cuatrimestresMinimosEstimados": {
-      "type": "number"
-    },
-    "materiasHabilitadasRanking": {
-      "type": "array"
-    },
-    "mensaje": {
-      "type": "string"
-    },
-    "plan": {
-      "type": "string"
-    },
-    "sugerenciaProximoCuatrimestre": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "totalMateriasPendientes": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "totalMateriasPendientes",
-    "cuatrimestresMinimosEstimados",
-    "materiasHabilitadasRanking",
-    "sugerenciaProximoCuatrimestre",
-    "mensaje"
-  ],
-  "type": "object"
-}New value: +null
  2. First observedv1.0.6

TDQS

A3.9/5.0
Behavior4/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 useful behavioral detail about the computation itself: transitive closure of unlocked subjects, critical-path height, and minimum-semester estimation. It does not discuss data freshness or assumptions, which keeps it from a 5.

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?

The definition is a single dense sentence that front-loads the main action ('Rankea') and then explains the metrics computed. It is efficient, though the parenthetical and stacked technical terms make it slightly harder to parse than an ideal definition.

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 only two parameters, no nested objects, and no output schema, the description does a reasonable job of stating what the tool returns: ranked subjects plus critical-path and minimum-semester estimates. It could be more explicit about the output structure or ordering, but the core computational result is conveyed.

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 in the schema. The description does not add syntax, format, or selection guidance for 'carrera' or 'max_sugerencias' beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it ranks enabled subjects by their multiplier impact in the prerequisite graph, and additionally computes critical-path height and minimum semesters to graduate. This clearly distinguishes it from a plain listing tool such as guarani_materias_habilitadas, even without naming that sibling.

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?

Usage is only implied: the mention of 'materias habilitadas para cursar' and 'próximo cuatrimestre' suggests academic planning, but there is no explicit when-to-use guidance, no prerequisites, and no statement of when to prefer this over guarani_materias_habilitadas or guarani_correlatividades_y_plan.

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