Skip to main content
Glama
Brightspace Facultad MCP

Brightspace Facultad MCP

listar_tareas

Read-only

Lists activities for a course with status and original due dates, helping identify pending work; use the related reading tool to view assignment prompts.

Instructions

Lista actividades de una materia con estado y vencimiento original; usa leer_tarea para la consigna.

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_tareas"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
limiteNo
materia_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description adds that results carry state and original due date, but says nothing about pagination behavior (cursor/limite) or result volume, which matters for a listing tool that returns an open-ended collection.

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?

A single compact clause pair: capability first, alternative second. No filler, and the most important information is front-loaded.

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?

Because an output schema exists, the description needn't explain return values, and annotations cover the safety profile. Still, for a paginated list tool with three undocumented parameters, the description leaves real gaps an agent must guess about.

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 compensate and it does not: materia_id, cursor and limite are never mentioned. The only hint is that activities belong to a 'materia', which implicitly maps to materia_id but leaves the pagination parameters entirely unexplained.

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 gives a specific verb+resource ('Lista actividades de una materia') and scopes it further by noting it returns estado and vencimiento original, so an agent can tell it apart from leer_tarea, the sibling that fetches the consigna.

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?

It explicitly routes the agent to leer_tarea when the task statement/consigna is needed, which is a clear alternative-selection hint. It does not state when-not to use this tool or mention the other listing siblings, so it stops short of full guidance.

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