Skip to main content
Glama

Progreso de Carrera y Materias Faltantes para Recibirse

guarani_progreso_carrera
Read-onlyIdempotent

Calculates how many courses remain to graduate in SIU Guaraní, including approved, in-progress, and pending courses by year for a given degree.

Instructions

Calcula exactamente cuántas materias te faltan para recibirte en SIU Guaraní ('Te faltan X materias'), cuántas tenés aprobadas, cursando actualmente y el desglose de materias pendientes por año.

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_progreso_carrera"
  }
}

Input Schema

NameRequiredDescriptionDefault
carreraNoNombre o código de la carrera en Guaraní

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": {
      -    "aprobadas": {
      -      "type": "number"
      -    },
      -    "carrera": {
      -      "type": "string"
      -    },
      -    "cursando": {
      -      "type": "number"
      -    },
      -    "faltantesParaRecibirse": {
      -      "type": "number"
      -    },
      -    "materiasEnCurso": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "materiasRestantesPorAnio": {
      -      "additionalProperties": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "type": "object"
      -    },
      -    "mensaje": {
      -      "type": "string"
      -    },
      -    "plan": {
      -      "type": "string"
      -    },
      -    "porcentajeAvance": {
      -      "type": "number"
      -    },
      -    "regularizadas": {
      -      "type": "number"
      -    },
      -    "totalMaterias": {
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "totalMaterias",
      -    "aprobadas",
      -    "faltantesParaRecibirse",
      -    "cursando",
      -    "regularizadas",
      -    "materiasEnCurso",
      -    "materiasRestantesPorAnio",
      -    "mensaje"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. First observedv1.0.6

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds that the calculation is exact and enumerates what is reported (approved, in-progress, pending by year), but says nothing about data freshness, whether it requires an active Guaraní session, or what happens when no career is specified.

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 with the key promise ('Te faltan X materias') up front and no filler. It is dense but every clause maps to real output content; minor tightening would make it a 5.

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 no output schema, the description usefully enumerates the returned figures (remaining, approved, in-progress, per-year breakdown), which is the main completeness burden here. The one gap is the behavior when the optional 'carrera' parameter is omitted, plus no routing against similar academic-history siblings.

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 there is only one parameter, so the baseline is 3. The description never mentions 'carrera', nor that it is optional (0 required parameters) — presumably defaulting to the student's active career — which would have been valuable added meaning.

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 ('Calcula') and a well-defined resource: remaining subjects to graduate, approved/in-progress counts, and pending breakdown by year. An agent can picture the exact output. It does not, however, distinguish itself from overlapping siblings such as guarani_historia_academica or guarani_plan_optimo, which likely return related academic data.

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 use case ('cuántas materias te faltan para recibirte') is clearly implied, so an agent knows when this tool is relevant. There is no explicit when-not guidance and no sibling is named as the alternative for related questions, leaving the boundary with historia_academica/estado_cursada to inference.

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