Skip to main content
Glama

Plan de Estudios, Correlatividades e Impacto en Guaraní

guarani_correlatividades_y_plan
Read-onlyIdempotent

Query interactive curriculum plans, subjects by year, approval status, and prerequisites for coursework and final exams; analyze blocking prerequisites and dependent future subjects.

Instructions

Consulta el plan de estudios interactivo, materias por año, estado de aprobación y correlatividades para cursar y rendir final. Si se especifica una materia, analiza qué correlativas la traban y qué materias futuras dependen de ella.

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

Input Schema

NameRequiredDescriptionDefault
carreraNoNombre o código de la carrera (opcional)
materiaNoNombre o código de la materia a analizar (opcional)

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": {
      -    "analisisCompleto": {
      -      "type": "boolean"
      -    },
      -    "analisisMateria": {
      -      "additionalProperties": {},
      -      "type": "object"
      -    },
      -    "materias": {
      -      "type": "array"
      -    },
      -    "materiasHabilitadasParaCursar": {
      -      "type": "array"
      -    },
      -    "materiasSinVerificar": {
      -      "type": "number"
      -    },
      -    "plan": {
      -      "type": "string"
      -    },
      -    "propuesta": {
      -      "type": "string"
      -    },
      -    "resumenImpacto": {
      -      "type": "string"
      -    },
      -    "version": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "materias"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. First observedv1.0.6

TDQS

A3.8/5.0
Behavior4/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. The description adds a genuinely non-obvious behavioral trait: when a materia is supplied, it performs a two-directional dependency analysis (blocking prerequisites and dependent future subjects). It does not describe the shape of the returned plan data, which is a minor gap given annotations carry the safety burden.

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?

Two sentences, front-loaded with the primary purpose followed by the conditional-mode behavior. No filler, though the first sentence packs four separate outputs into one clause, which slightly dilutes scannability.

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?

For a read-only informational query with only two optional params and full schema coverage, the description is largely sufficient, and annotations cover the safety profile. The one missing piece is any hint of what the returned plan/correlativity data looks like, since there is no output schema, but this is a minor gap for a lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both params are already documented as optional strings with name-or-code semantics. The description adds real value beyond the schema by explaining what supplying materia actually does — analyzing which correlativas block it and which future subjects depend on it — which is more than the schema's 'materia a analizar'.

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 resource (plan de estudios interactivo, materias por año, estado de aprobación, correlatividades), so the agent knows it is a read query over the curriculum. However, 'estado de aprobación' and curriculum planning overlap conceptually with siblings like guarani_progreso_carrera and guarani_plan_optimo, and the description makes no attempt to distinguish itself from them.

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 second sentence implies usage context: 'Si se especifica una materia' triggers a dependency analysis, which tells the agent the optional materia param switches behavior. But there is no explicit when-to-use/when-not guidance and no naming of alternatives (progreso_carrera, plan_optimo, materias_habilitadas), so the agent must infer which tool fits its need.

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