Skip to main content
Glama
Brightspace Facultad MCP

Brightspace Facultad MCP

leer_tarea

Read-only

Read an assignment's prompt, due date, status, and materials by passing the task ID returned from the assignment list.

Instructions

Lee consigna, vencimiento, estado y materiales de un ID obtenido con listar_tareas.

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": {
      "tarea_id": "<tarea_id>"
    },
    "name": "leer_tarea"
  }
}

Input Schema

NameRequiredDescriptionDefault
tarea_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 carried by structured data. The description adds which fields are exposed, but says nothing about session/auth requirements or what happens with an invalid or inaccessible ID — relevant given the openWorldHint and the existence of iniciar_sesion.

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?

One short sentence with no filler: verb, returned fields, and input provenance all front-loaded in a single clause chain. Nothing is extraneous, though the phrasing packs the field list in a way that reads slightly dense.

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?

With an output schema present, return-value explanation is not required, and the annotations cover read-only safety. What is missing is operational context for a networked, authenticated read: failure modes for an unknown ID or expired session, which matters for a single-required-parameter fetch tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage, so the schema alone leaves tarea_id undocumented. The description compensates meaningfully by stating the ID is the one obtained from listar_tareas, but it does not state the format (numeric vs string, course-scoped uniqueness) or error behavior for a bad ID.

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 uses a specific verb (lee) plus the resource (tarea identified by ID) and enumerates exactly what is retrieved: consigna, vencimiento, estado y materiales. That is far more specific than a tautology and distinguishes it from siblings like listar_tareas or leer_documento, though it does not explicitly contrast with the latter.

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 names the prerequisite and provenance of the input: the ID must come from listar_tareas, which tells an agent the intended call order. It stops short of stating exclusions or when to prefer a different reader, so it is clear context rather than a full when/when-not rule set.

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