Skip to main content
Glama

Historia Académica y Analítico en Guaraní

guarani_historia_academica
Read-onlyIdempotent

Fetches a student's academic history from SIU Guaraní to show approved final exams, pending subjects, grades, and averages, optionally filtered by career.

Instructions

Analítico completo: finales aprobados, materias pendientes, notas y promedios en SIU Guaraní.

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

Input Schema

NameRequiredDescriptionDefault
carreraNoNombre o código de la carrera (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": {
      -    "carrera": {
      -      "type": "string"
      -    },
      -    "carrerasDisponibles": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "materiasAprobadas": {
      -      "type": "array"
      -    },
      -    "materiasRegulares": {
      -      "type": "array"
      -    },
      -    "porcentajeAvance": {
      -      "type": "number"
      -    },
      -    "promedioConAplazos": {
      -      "type": "number"
      -    },
      -    "promedioSinAplazos": {
      -      "type": "number"
      -    },
      -    "totalAprobadas": {
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "totalAprobadas",
      -    "materiasAprobadas",
      -    "materiasRegulares"
      -  ],
      -  "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 state readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the scope of returned data but says nothing about authentication/session prerequisites, behavior when carrera is omitted, or pagination. For a read-only tool with complete annotations, 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the key noun 'Analítico completo' comes first and the list of contents follows immediately.

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?

The description lists what the tool returns, which is helpful given there is no output schema. However, it omits prerequisites (e.g., SIU Guaraní login/session) and does not clarify what happens without the optional carrera filter, leaving gaps for an agent that must decide whether it can call this tool directly.

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?

There is only one optional parameter (carrera) and schema description coverage is 100%, so the schema already explains its semantics. The description never mentions the parameter or its default behavior, which puts it at the baseline 3 for high-coverage schemas.

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?

The description names a specific resource ('Analítico completo') and enumerates its contents (finales aprobados, materias pendientes, notas, promedios) within SIU Guaraní, which lets an agent distinguish it from partial-status siblings like guarani_estado_cursada or guarani_progreso_carrera. It does not name those siblings explicitly, so it stops short of a 5.

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 word 'completo' implicitly signals that this tool returns the full transcript rather than a partial view, which is a weak cue for choosing it over guarani_progreso_carrera or guarani_estado_cursada. There is no explicit when-to-use, when-not-to-use, or alternative named.

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