Skip to main content
Glama

Historial de Solicitudes de Constancias en Guaraní

guarani_historial_constancias
Read-onlyIdempotent

Retrieves your SIU Guaraní history of certificate and transcript requests, with optional automatic PDF downloads for issued documents.

Instructions

Consulta el historial de solicitudes de constancias y certificados emitidos en SIU Guaraní, con opción de descarga de PDFs.

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

Input Schema

NameRequiredDescriptionDefault
carreraNoNombre o código de la carrera
descargarNoSi es true, descarga automáticamente los archivos PDF disponibles (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / descargar / default
      Removed value: -false
    • changedInput schema / properties / descargar / description
      Previous value: -"Si es true, descarga automáticamente los archivos PDF disponibles"New value: +"Si es true, descarga automáticamente los archivos PDF disponibles (por defecto: false)"
  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": {
      -    "solicitudes": {
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "solicitudes"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. First observedv1.0.6

TDQS

A3.6/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 the safety profile is covered. The description adds only the side effect that PDFs may be auto-downloaded when requested; it says nothing about where files land, whether the query is scoped to the authenticated student, or pagination.

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 well-formed sentence with zero padding, front-loading both the resource and the notable download option.

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 simple read-only, two-optional-parameter tool with a fully documented schema and no output schema, this is nearly sufficient: it names the source system and the kind of records returned. Only ambiguity about result shape/scope (own history only? all carreras by default?) keeps it from a 5.

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 both parameters are fully documented in the schema; baseline is 3. The description adds no extra semantics beyond the schema (it never explains that 'carrera' filters the history by degree program).

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?

Uses a specific verb ('Consulta') with a precise resource ('historial de solicitudes de constancias y certificados emitidos en SIU Guaraní') and mentions the optional PDF download. It does not explicitly distinguish itself from the nearest sibling, guarani_certificado_alumno_regular, which likely creates/requests a certificate rather than listing past ones.

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: an agent can infer this is the tool for reviewing previously issued certificates, but there is no explicit 'use this when...' statement nor a pointer to the sibling that handles new certificate requests.

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