Skip to main content
Glama

listar_archivos

Read-only

Lists folders and materials from a Teams course's General channel, enabling document browsing and retrieval of folder IDs for deeper navigation.

Instructions

Lista carpetas y materiales del canal General; carpeta_id se obtiene del listado anterior.

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": {
      "materia_id": "<materia_id>"
    },
    "name": "listar_archivos"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
limiteNo
carpeta_idNo
materia_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful navigation fact that carpeta_id comes from a prior listing, but says nothing about pagination behavior, ordering, or what happens when carpeta_id is null (listing root vs. a folder). Since an output schema exists, return-value detail is not required.

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?

A single compact sentence with no filler, and the resource being listed is stated up front. Nothing is redundant, though the brevity comes at the cost of the missing parameter guidance noted elsewhere.

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

Completeness2/5

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

With four parameters at 0% schema coverage and a required materia_id, the definition is under-specified for correct invocation. The presence of an output schema removes the need to describe returns, but the prerequisites and pagination semantics an agent needs are absent.

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 parameter meaning, yet it only addresses carpeta_id and only its provenance. The required materia_id is never explained, and cursor and limite are not mentioned at all, leaving three of four parameters with no semantic guidance beyond their names and defaults.

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

Purpose3/5

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

The verb and resource are concrete ("Lista carpetas y materiales"), so the agent knows it enumerates folders and materials. However, the description scopes it to "el canal General" while the schema requires a materia_id, leaving ambiguous whether listing is per-materia or global. It also does not differentiate itself from siblings such as listar_materias or leer_documento.

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

Usage Guidelines2/5

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

The only guidance is the implicit workflow hint that carpeta_id "se obtiene del listado anterior", indicating a drill-down navigation pattern. There is no statement of when to use this versus leer_documento or leer_tarea, no prerequisites, and no exclusions.

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