Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

ver_tarea

Read-only

Retrieve assignment details—brief, attachments, opening/due/cutoff dates, allowed submission format, and your submission status—to check requirements and progress.

Instructions

Detalle de una tarea: enunciado, archivos adjuntos del enunciado, fechas (apertura, vencimiento, corte), formato de entrega permitido y el estado de tu entrega (archivos enviados, nota y comentarios).

tarea_id es el recurso_id que dan proximas_entregas o contenido_ramo. Muchas tareas traen el enunciado solo como PDF adjunto: bájalo con descargar_material(ramo, recurso_id=tarea_id).

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

Input Schema

NameRequiredDescriptionDefault
ramoNo
tarea_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds beyond that: it discloses that data returned is scoped to 'tu entrega' (the caller's own submission) and warns that many tasks expose the statement only as a PDF that must be fetched separately via descargar_material, a genuine workflow caveat.

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 tight paragraphs: the first front-loads what the tool returns, the second handles the ID mapping and the PDF workaround. The embedded call syntax 'descargar_material(ramo, recurso_id=tarea_id)' is slightly informal but earns its place by making the follow-up actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with two parameters and an existing output schema, the description covers the important gaps: ID provenance, the PDF-only statement pitfall, and the fact that returned submission status is the caller's own. The only omission is a definition of 'ramo', which is minor given the tool's simplicity.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It fully explains tarea_id by mapping it to the recurso_id emitted by other tools, which is valuable, but the 'ramo' parameter is never defined — it only appears incidentally inside the descargar_material call example, leaving the agent to infer that it scopes to a course.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb+resource ('Detalle de una tarea') and enumerates exactly what is returned: statement, attachments, dates (apertura/vencimiento/corte), allowed submission format, and the status of the user's own submission. That level of specificity distinguishes it from siblings like ver_notas or leer_material without needing to inspect the schema.

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 tells the agent where tarea_id comes from (proximas_entregas or contenido_ramo) and explicitly routes the PDF-statement case to descargar_material, which is real alternative-tool guidance. It does not state exclusions — e.g. that grades alone belong to ver_notas — so it falls short of the explicit when/when-not bar.

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