Skip to main content
Glama

leer_archivo

Downloads a Moodle file from a pluginfile URL and extracts text from PDF, Word, PowerPoint, HTML, or plain text; returns images and saves unsupported formats to disk.

Instructions

Descarga un archivo de Moodle (URL de pluginfile que aparece en ver_tarea, ver_curso o ver_discusion). Extrae el texto de PDF, Word (.docx), PowerPoint (.pptx), páginas HTML y texto; devuelve imágenes; otros formatos se guardan en disco.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "leer_archivo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesfileurl del archivo en Moodle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the main behavioral differentiator: output depends on format (text extraction, image return, or disk write). It omits permission/auth requirements, size limits, and what happens on unsupported or corrupt files, which are real gaps for a download tool.

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 the action first, the input source second, and the format matrix last. No filler and no redundancy with the schema or title.

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 one-parameter tool with a fully documented schema and no output schema, the description covers purpose, input provenance, and per-format outcomes well. It could be complete with a note on failure modes or whether the disk-saved path is returned, but nothing essential to invoking it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one parameter, so the baseline is 3. The description adds genuine meaning by specifying that the URL is a pluginfile URL obtained from sibling tools, clarifying a constraint the schema's 'fileurl del archivo en Moodle' does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Descarga un archivo de Moodle') and then enumerates exactly what it does with the content: text extraction for PDF/DOCX/PPTX/HTML/text, image return, disk save for everything else. This is far more than a restatement of the name and makes the tool's role unmistakable against siblings like ver_tarea, which only surface the URL.

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

Usage Guidelines4/5

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

Explicitly tells the agent where the input comes from ('URL de pluginfile que aparece en ver_tarea, ver_curso o ver_discusion'), which is the key routing hint needed to chain this tool after a listing tool. It does not state when NOT to use it or what to do if no pluginfile URL is present, so it stops short of full when/when-not guidance.

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