Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

leer_material

Idempotent

Reads PDF or text course materials and saves a local copy so you can review assignment briefs, guides, or notes; supports page ranges for long PDFs.

Instructions

Lee el contenido de un archivo del ramo (PDF o texto) y además lo deja guardado en su carpeta local.

Úsalo para entender un enunciado, una guía o un apunte. Identifica el archivo por recurso_id (de contenido_ramo o ver_tarea) y, si el recurso tiene varios, por parte del nombre en archivo. Devuelve hasta ~30 000 caracteres; para PDFs largos pide un rango con paginas='3-6'. No extrae imágenes ni fórmulas dibujadas: si hacen falta, abre el archivo de guardado_en.

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": {
      "ramo": "<ramo>"
    },
    "name": "leer_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
ramoYes
archivoNo
paginasNo
recurso_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description explains the otherwise surprising readOnlyHint=false by stating the file is also saved to a local folder, and it discloses a real output cap (~30 000 caracteres), the pagination escape hatch with syntax, and an extraction limitation (no images or drawn formulas). What it does not cover is what happens on failure, overwrite behavior in the local folder, or whether repeated calls re-download — relevant for an idempotent write.

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?

Four short blocks in a deliberate order: what it does, when to use it, how to identify the file, then limits and fallbacks. No filler sentences and the side effect is front-loaded in the first sentence.

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?

An output schema exists, so the description correctly avoids describing return values, yet it still flags the character cap and references the guardado_en field as a follow-up path. The undefined 'ramo' parameter and the absence of any error or overwrite behavior keep it from being fully complete for a four-parameter tool with a write side effect.

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?

With schema description coverage at 0%, the description carries the load and does most of it: recurso_id is tied to output of contenido_ramo or ver_tarea, archivo is explained as a partial-name disambiguator when a resource has multiple parts, and paginas is given a concrete example format ('3-6'). Only 'ramo' is left unexplained, which is the main residual gap.

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?

Names a specific verb and resource ('Lee el contenido de un archivo del ramo') and adds the scope of formats (PDF o texto) plus the side effect of saving it locally. It is distinguishable from content-listing siblings because it points to where the identifier comes from (contenido_ramo, ver_tarea), though it never explicitly contrasts itself with a bulk-download sibling.

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?

'Úsalo para entender un enunciado, una guía o un apunte' gives a concrete use case, and the closing sentence supplies a fallback path ('abre el archivo de guardado_en') when images or formulas are needed. There is no explicit statement of when not to use it or which sibling to prefer for other tasks, so it stops short of full routing guidance.

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