Skip to main content
Glama

leer_documento

Read-only

Extracts text from DOCX, PPTX, or PDF files up to 25 MiB in paginated chunks so AI assistants can read course documents; no OCR, and viewer-based files may return partial text.

Instructions

Extrae texto de DOCX, PPTX o PDF (máximo 25 MiB) en fragmentos. Sin OCR; puede devolver texto parcial del visor.

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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=true, destructive=false), and the description adds real behavioral context: a 25 MiB size ceiling, chunked response, no OCR fallback, and the possibility of partial text extracted by the viewer. It stops short of saying what happens when a chunk is empty or how pagination terminates.

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?

Two compact clauses, front-loaded with the core action and formats, followed by limits and caveats. No sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a 3-parameter tool with 0% schema coverage and an existing login/listing sibling set, the missing archivo_id provenance and cursor semantics leave a real gap.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the three parameters, and it does not. 'En fragmentos' hints at the cursor/limite_caracteres mechanism but never explains that limite_caracteres caps chunk size (max 10000) or that cursor continues extraction, and it never says where archivo_id comes from.

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?

The description names a specific verb and resource (extract text from DOCX, PPTX, PDF), plus scope constraints (max 25 MiB) and output shape (in chunks). This clearly distinguishes it from the listing and task/announcement siblings without needing to name them.

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?

Usage is only implied: an agent infers this is the tool for reading document contents, and 'Sin OCR' hints at when it will not work (scanned documents). There is no explicit instruction on when to pick this over listar_archivos or how to obtain archivo_id first, and no stated prerequisites.

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