Skip to main content
Glama
Sign In
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Historial de Solicitudes de Constancias en Guaraní

guarani_historial_constancias
Read-onlyIdempotent

Retrieve the history of certificate and constancia requests issued in SIU Guaraní, with optional PDF downloads.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
carreraNoNombre o código de la carrera
descargarNoSi es true, descarga automáticamente los archivos PDF disponibles

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": {
-    "solicitudes": {
-      "type": "array"
-    }
-  },
-  "required": [
-    "solicitudes"
-  ],
-  "type": "object"
-}New value: +null
  2. 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=true, idempotentHint=true, and openWorldHint=true. The description adds useful context that PDF downloads are optional, but it does not explain what the download does, whether authentication is required, or what the returned history contains.

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 wasted language. It states the core action and the optional download behavior efficiently.

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 two-parameter read-only tool with full schema coverage and annotations, the description is largely sufficient. The main gap is that it does not describe the shape of the returned history, but the overall purpose and optional download behavior are clear.

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 already well documented. The description mentions the PDF download option, which corroborates the 'descargar' parameter, but adds no new meaning beyond the schema.

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 (historial de solicitudes de constancias y certificados) in SIU Guaraní. It is clear what the tool retrieves, but it does not explicitly distinguish itself from sibling tools such as guarani_certificado_alumno_regular, which likely handles new certificate requests.

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 description implies the tool is for checking past certificate requests and optionally downloading PDFs, but it gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent must infer that this is not the tool for requesting a new certificate.

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