Skip to main content
Glama

Plan Óptimo de Cursada y Desbloqueo de Correlatividades

guarani_plan_optimo
Read-onlyIdempotent

Ranks available courses by how many prerequisites they unlock, suggests next-semester priorities, and estimates critical-path and minimum semesters to graduate for a degree.

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.

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": "guarani_plan_optimo"
  }
}

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. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / max_sugerencias / default
      Removed value: -5
  2. 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
  3. 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 destructiveHint=false, so the safety profile is covered and the description does not contradict it. What it adds is the deterministic nature of the computation (transitive closure over the prerequisite graph), but it says nothing about data dependencies, what happens when the student's current state is incomplete, or how the estimation is bounded.

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 dense sentence with the action front-loaded and no filler; every clause carries a distinct computational output. It leans slightly jargon-heavy ("cierre transitivo", "altura del camino crítico") which may cost a non-specialist agent, but nothing is wasted.

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 carries the return-value burden and does partly deliver by enumerating the three outputs (ranking, critical-path height, minimum semesters). It is still incomplete for a tool with all-optional inputs: nothing explains what happens if carrera is omitted, nor the assumed baseline state of the student's cursada.

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 documented in-schema, including the default of 5 and the 1-10 range, so the baseline applies. The description adds no semantics beyond the schema, and does not address the notable fact that carrera is optional (0 required), leaving the no-argument behavior unexplained.

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?

Precise verb pair ("Rankea ... y calcula") applied to a specific resource (materias habilitadas + grafo de correlatividades), with the metric named explicitly (cierre transitivo de materias desbloqueadas). It never differentiates itself from the adjacent siblings that also expose habilitadas/correlatividades data (guarani_materias_habilitadas, guarani_correlatividades_y_plan), so an agent cannot rule those out from the description alone.

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?

When-to-use is only implied: an advisory ranking of next-cuatrimestre options emerges from the wording, but there is no explicit trigger case, no stated prerequisite (e.g. requires the student's academic history), and no named alternative to prefer for plain listing or graph inspection. The agent must infer selection from the purpose sentence.

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