Skip to main content
Glama
Brightspace Facultad MCP

Brightspace Facultad MCP

listar_materias

Read-only

Lists visible courses from My Courses with opaque IDs and optional pagination, helping you find available course identifiers. Results may not include every enrollment.

Instructions

Lista cursos visibles de Mis cursos con IDs opacos. Puede haber filtros; no garantiza todas las inscripciones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listar_materias"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
limiteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful caveat beyond the annotations: results are not guaranteed to include all enrollments, so the agent knows the list may be partial. However, it omits pagination behavior and the 'opaque IDs' remark is not explained, so the added context is thin for a tool with openWorldHint=true.

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?

Two short sentences with the resource scope front-loaded and no filler wording. The brevity is appropriate, though the second sentence packs two vague claims ('puede haber filtros', 'no garantiza') that would be better as one precise caveat.

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 explained, but the two input parameters are entirely undocumented and the incompleteness caveat is left unqualified (incomplete in what sense — enrollment state, visibility, paging?). For a paginated, open-world listing tool the description leaves an agent guessing on both paging and result coverage.

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 coverage is 0%, so the description carries the full burden for the two parameters (cursor, limite) and says nothing about either — no mention of paging semantics or the 1-100 limit range. Worse, 'Puede haber filtros' hints at filters that do not exist in the schema, which is actively misleading rather than merely silent.

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 opens with a specific verb+resource pair ('Lista cursos visibles de Mis cursos'), which lets an agent distinguish this from siblings like listar_archivos or listar_tareas without opening the schema. The added qualifier about opaque IDs narrows the resource further, though the term 'Mis cursos' is never defined and no sibling is named explicitly.

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?

There is no when-to-use guidance at all: nothing says when to pick this over leer_documento or listar_tareas, and no prerequisites are stated. The sentence 'Puede haber filtros' is hedging rather than guidance and, given the schema exposes only cursor and limite, it actually muddies the picture.

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