Skip to main content
Glama
Brightspace Facultad MCP

Brightspace Facultad MCP

listar_archivos

Read-only

Lists units, modules, and topics in Brightspace course Content using course and folder IDs, and updates reading progress for tracked materials.

Instructions

Lista unidades, módulos y temas de Contenido. carpeta_id proviene de un listado anterior. Puede actualizar el progreso de lectura.

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.4/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, yet the description states 'Puede actualizar el progreso de lectura', which asserts a write side effect. The agent cannot know whether this call mutates state, and the conflicting claim undermines the structured safety profile without clarifying permissions, scope, or reversibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, and the purpose statement is front-loaded. The final sentence, however, is vague ('Puede actualizar...') and spends space creating ambiguity rather than resolving it.

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?

An output schema exists, so return values need not be described. But with four parameters at 0% schema coverage, pagination unaddressed, and contradictory mutation language versus readOnlyHint=true, the description leaves an agent without enough information to call this correctly or predict its effects.

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 carries the full burden, and it only explains carpeta_id's provenance. materia_id (required), cursor and limite (pagination) receive no semantics at all, leaving three of four parameters undocumented in both schema and prose.

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?

The description names a specific verb ('Lista') and concrete resources (unidades, módulos y temas de Contenido), so the agent can tell it enumerates a content hierarchy. However, it gives no hint about how it differs from siblings such as listar_materias or listar_tareas, so the scope boundary is left implicit.

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?

'carpeta_id proviene de un listado anterior' is the only usage signal: it establishes a prerequisite chaining rule, which is genuinely useful. There is no guidance on when to call this instead of listar_materias/listar_tareas, no mention of pagination via cursor/limite, and no exclusions.

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