Skip to main content
Glama
Brightspace Facultad MCP

Brightspace Facultad MCP

leer_documento

Read-only

Read HTML and PDF/DOCX/PPTX course documents up to 25 MiB in chunks to extract Brightspace materials; excludes quizzes/assignments and does not use OCR, so viewer output may be partial.

Instructions

Lee páginas HTML y PDF/DOCX/PPTX (máximo 25 MiB) por fragmentos. No abre cuestionarios ni asignaciones como documentos. Sin OCR; el visor puede ser parcial.

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": {
      "archivo_id": "<archivo_id>"
    },
    "name": "leer_documento"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
archivo_idYes
limite_caracteresNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds real behavioral context beyond them: a 25 MiB cap, no OCR (scanned PDFs will fail), and the warning that the viewer may be partial, i.e. returned content may be incomplete. It does not explain what triggers a partial view or how errors surface, which keeps it below a 5.

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?

Three short sentences, front-loaded with the capability, followed by the exclusion and then the limitations. Nothing is repeated and no sentence could be dropped without losing information.

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?

Because an output schema exists, return values need not be described, and the description covers formats, size limit, exclusions, OCR absence and partial-view risk. The remaining gap is procedural: how to obtain archivo_id and how to chain the cursor across calls.

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?

With 0% schema description coverage the description must carry parameter meaning, and it only partly does: "por fragmentos" implies cursor-based pagination and a chunk size, but cursor format, whether it comes from a prior response, and where archivo_id originates (e.g. listar_archivos) are all left unstated.

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?

"Lee páginas HTML y PDF/DOCX/PPTX ... por fragmentos" names a specific verb, the exact resource types, and the chunked delivery mode. The second sentence carves out an explicit boundary ("No abre cuestionarios ni asignaciones como documentos"), so an agent can distinguish it from leer_tarea/leer_anuncios without inspecting schemas.

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?

The description tells the agent when this tool is NOT the right choice (quizzes/assignments are handled elsewhere) and implies it is the tool for reading document file content by fragment. It stops short of naming the sibling tools to use instead, so the routing is clear in context but not fully explicit.

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