Skip to main content
Glama
Sign In
UCA MCP

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Solicitud y Descarga de Constancia de Alumno Regular en Guaraní

guarani_certificado_alumno_regular

Issues and downloads a formal PDF certificate of regular student status, approved activities, or academic average from SIU Guaraní with an institutional validation code after user confirmation.

Instructions

Emite y descarga formalmente en PDF la Constancia de Alumno Regular (o de actividades aprobadas/promedio) con código de validación institucional desde SIU Guaraní. Protegida por confirmación del usuario.

Input Schema

NameRequiredDescriptionDefault
copiasNoCantidad de copias a solicitar (1 a 5) (por defecto: 1)
carreraNoNombre o código de la carrera
presentar_aNoDestinatario ante quien se presentará la constancia (por defecto: A quien corresponda)
forzar_nuevaNoSi es true, fuerza la emisión de una nueva solicitud en Guaraní omitiendo constancias ya emitidas (por defecto: false)
observacionesNoObservaciones adicionales opcionales
tipo_constanciaNoTipo de constancia institucional a solicitar (por defecto: alumno_regular)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.1.0
    • removedInput schema / properties / copias / default
      Removed value: -1
    • changedInput schema / properties / copias / description
      Previous value: -"Cantidad de copias a solicitar (1 a 5)"New value: +"Cantidad de copias a solicitar (1 a 5) (por defecto: 1)"
    • removedInput schema / properties / forzar_nueva / default
      Removed value: -false
    • changedInput schema / properties / forzar_nueva / description
      Previous value: -"Si es true, fuerza la emisión de una nueva solicitud en Guaraní omitiendo constancias ya emitidas"New value: +"Si es true, fuerza la emisión de una nueva solicitud en Guaraní omitiendo constancias ya emitidas (por defecto: false)"
    • removedInput schema / properties / presentar_a / default
      Removed value: -"A quien corresponda"
    • changedInput schema / properties / presentar_a / description
      Previous value: -"Destinatario ante quien se presentará la constancia"New value: +"Destinatario ante quien se presentará la constancia (por defecto: A quien corresponda)"
    • removedInput schema / properties / tipo_constancia / default
      Removed value: -"alumno_regular"
    • changedInput schema / properties / tipo_constancia / description
      Previous value: -"Tipo de constancia institucional a solicitar"New value: +"Tipo de constancia institucional a solicitar (por defecto: alumno_regular)"
  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": {
-    "aprobado": {
-      "type": "boolean"
-    },
-    "comprobante": {
-      "type": "string"
-    },
-    "copias": {
-      "type": "number"
-    },
-    "detalles": {
-      "additionalProperties": {},
-      "type": "object"
-    },
-    "exito": {
-      "type": "boolean"
-    },
-    "instruccion": {
-      "type": "string"
-    },
-    "mensaje": {
-      "type": "string"
-    },
-    "presentarA": {
-      "type": "string"
-    },
-    "rutaArchivoPdf": {
-      "type": "string"
-    },
-    "tipoConstancia": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "exito",
-    "mensaje"
-  ],
-  "type": "object"
-}New value: +null
  3. First observedv1.0.6

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare it is a non-read-only, non-idempotent, non-destructive, closed-world call; the description usefully adds what annotations cannot: the deliverable is a PDF with an institutional validation code, and the invocation is gated by an explicit user confirmation. It stops short of saying that an emission creates/records a new solicitud in Guaraní and that repeated calls may produce duplicates unless forzar_nueva is set.

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 verb, resource, output format and the confirmation constraint front-loaded before any detail. No filler, though the parenthetical variant list makes it slightly crowded.

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 6-parameter, fully documented, no-output-schema mutation tool this covers purpose and output format adequately but omits the two things an agent most needs: whether an active Guaraní session is required, and that emission creates a record (and may duplicate) unless forzar_nueva is true — plus no routing to guarani_historial_constancias.

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%, so all six parameters (copias, carrera, presentar_a, forzar_nueva, observaciones, tipo_constancia) are already documented in the schema. The description only echoes three of the five enum values and says nothing about the other parameters, so it matches the baseline rather than adding 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?

The description states a concrete verb pair (emite y descarga) and a concrete resource (Constancia de Alumno Regular, with variants actividades_aprobadas/promedio) produced as PDF from SIU Guaraní. It is clearly distinguishable from read-only siblings like guarani_historial_constancias, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the existing guarani_historial_constancias (view issued certificates) or when a new emission is warranted. The phrase 'Protegida por confirmación del usuario' gestures at a workflow but gives no actionable condition, exclusion, or prerequisite (e.g., active session).

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

Deploy Server

Other Tools