Skip to main content
Glama
Brightspace Facultad MCP

Brightspace Facultad MCP

leer_anuncios

Read-only

Reads visible announcements for a specified Brightspace course using its course ID, with optional pagination, so you can review course news. Opening announcements may mark them as read.

Instructions

Lee noticias visibles de la materia. Abrirlas puede marcarlas como leídas.

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": "leer_anuncios"
  }
}

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

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The sentence 'Abrirlas puede marcarlas como leídas' adds genuinely non-obvious behavioral context about a side effect, though it sits in tension with readOnlyHint and the description says nothing about pagination behavior or authentication needs.

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 no filler, and the core purpose is front-loaded before the side-effect caveat. It is efficient, though the sparseness means the second sentence carries almost all of the non-obvious information.

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 described, and annotations cover the safety profile. However, for a paginated list tool the definition never explains how cursor/limite interact or what 'visibles' filters out, leaving moderate gaps.

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 schema names the three parameters but explains none of them. The description only hints at materia_id ('de la materia') and scope ('visibles'); cursor and limite (default 10, max 100) get no explanation at all, leaving the pagination contract undocumented.

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 and resource ('Lee noticias visibles de la materia') and scopes it to the visible announcements of one subject, so an agent knows exactly what is returned. It does not name or distinguish itself from the sibling readers (leer_documento, leer_tarea), which keeps it short of a 5.

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 explicit when-to-use guidance: nothing says to prefer this over leer_documento or leer_tarea when fetching course content, and no prerequisites (e.g. the session established by iniciar_sesion) are mentioned. Usage is only inferable from the resource name.

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