Skip to main content
Glama
Sign In
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lectura de Archivos en EVA

eva_leer_archivo
Read-onlyIdempotent

Downloads EVA course files via HTTPS allowlist and extracts text from PDFs and Office documents, returning image blocks for scanned files.

Instructions

Descarga de forma segura (con allowlist HTTPS) y extrae texto de PDFs y Office, o retorna bloques de imagen en escaneados. Nota: La consulta de recursos o carpetas en EVA registra la visualización en la plataforma.

Input Schema

NameRequiredDescriptionDefault
urlNoURL completa del archivo o recurso en EVA (debe pertenecer a eva.uca.edu.ar)
cmidNoID numérico de la actividad o recurso (cmid) alternativo a la URL
max_paginasNoLímite de páginas a extraer (máx 50) (por defecto: 15)
desde_paginaNoPágina inicial desde donde extraer contenido (por defecto 1)
forzar_refrescoNoSi es true, omite la caché local y vuelve a descargar el archivo de EVA (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.0
    • removedInput schema / properties / desde_pagina / default
      Removed value: -1
    • removedInput schema / properties / forzar_refresco / default
      Removed value: -false
    • changedInput schema / properties / forzar_refresco / description
      Previous value: -"Si es true, omite la caché local y vuelve a descargar el archivo de EVA"New value: +"Si es true, omite la caché local y vuelve a descargar el archivo de EVA (por defecto: false)"
    • removedInput schema / properties / max_paginas / default
      Removed value: -15
    • changedInput schema / properties / max_paginas / description
      Previous value: -"Límite de páginas a extraer (máx 50)"New value: +"Límite de páginas a extraer (máx 50) (por defecto: 15)"
  2. Changed11 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / cmid / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / cmid / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / cmid / minimum
      Added value: +1
    • removedInput schema / properties / desde_pagina / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / desde_pagina / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / desde_pagina / minimum
      Added value: +1
    • removedInput schema / properties / max_paginas / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / max_paginas / minimum
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "filename": {
-      "type": "string"
-    },
-    "mimeType": {
-      "type": "string"
-    },
-    "proximaPagina": {
-      "type": "number"
-    },
-    "tamanoBytes": {
-      "type": "number"
-    },
-    "tipo": {
-      "type": "string"
-    },
-    "totalPaginas": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "filename",
-    "mimeType",
-    "tamanoBytes",
-    "tipo"
-  ],
-  "type": "object"
-}New value: +null
  3. First observedv1.0.6

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: HTTPS allowlist enforcement, extraction behavior differing by file type (text vs image blocks for scans), and a side-effect warning that querying resources/folders registers a visualization in the platform. That last detail is behavioral information annotations cannot express. It stops short of covering caching (forzar_refresco) implications.

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?

Two dense sentences, front-loaded with the primary action and result format. The trailing side-effect note earns its place, though its reference to 'consulta de recursos o carpetas' is slightly ambiguous about which operation is actually being persisted.

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?

With 5 optional parameters and no output schema, the description correctly spends its words explaining the return shape (text vs image blocks) and the access constraint. Missing only the url-vs-cmid decision guidance and cache behavior, which are moderate gaps rather than blocking ones.

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 coverage is 100%, so both the url constraint (must belong to eva.uca.edu.ar) and the cmid alternative are already documented in the schema. The description repeats the security constraint but adds nothing about choosing url vs cmid, pagination defaults, or cache override semantics.

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 chain (download safely, extract text, return image blocks) and names the exact resource types (PDF, Office, scanned). An agent knows what it gets back. It does not distinguish itself from the overlapping sibling eva_descargar_materiales, which keeps it from 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 purpose implies usage (fetch content from a specific file URL or cmid), but there is no explicit when-to-use/when-not guidance and no routing to eva_descargar_materiales or eva_buscar_materiales, even though those siblings overlap. Usage must be inferred.

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