Skip to main content
Glama

Mis Inscripciones a Examen Final en Guaraní

guarani_mis_inscripciones_examen
Read-onlyIdempotent

Retrieves a student's active final exam registrations and provisional academic records from SIU Guaraní, optionally filtered by career and refreshed past the cache.

Instructions

Consulta las inscripciones activas a mesas de examen final y actuaciones provisorias del alumno 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_mis_inscripciones_examen"
  }
}

Input Schema

NameRequiredDescriptionDefault
carreraNoNombre o código de la carrera
forzar_refrescoNoSi es true, ignora la caché de 45-60 s y consulta de nuevo (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / forzar_refresco / default
      Removed value: -false
    • changedInput schema / properties / forzar_refresco / description
      Previous value: -"Si es true, ignora la caché de 45-60 s y consulta de nuevo"New value: +"Si es true, ignora la caché de 45-60 s y consulta de nuevo (por defecto: false)"
  2. Changed4 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / forzar_refresco
      Added value: +{
      +  "default": false,
      +  "description": "Si es true, ignora la caché de 45-60 s y consulta de nuevo",
      +  "type": "boolean"
      +}
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "inscripciones": {
      -      "type": "array"
      -    },
      -    "mensaje": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "inscripciones",
      -    "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, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds useful scope cues ('activas', 'actuaciones provisorias'), but says nothing about the caching behavior (the 45-60 s cache is only disclosed in the schema) or what is returned.

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 no filler that states the resource and scope immediately. Appropriate length for a read-only lookup tool.

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?

For a two-optional-param read-only tool with no output schema and annotations covering safety, the description is minimally adequate. It does not indicate what the result contains (mesa, fecha, estado, condición de provisoria) or what an empty result means.

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 (carrera, forzar_refresco) are fully documented in the schema, including the cache semantics. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 (inscripciones activas a mesas de examen final y actuaciones provisorias) scoped to the student. It is distinguishable from guarani_mesas_disponibles (offerings) and guarani_inscribir_examen (action), but never names those siblings explicitly.

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 by the phrase 'inscripciones activas... del alumno'; there is no explicit statement of when to prefer this over guarani_mesas_disponibles or guarani_inscribir_examen. An agent must infer the routing from the names alone.

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