Skip to main content
Glama

ver_tarea

Displays a complete Moodle assignment, including instructions, due dates, attachments, your submission status, and feedback so you can review requirements and progress.

Instructions

Muestra una tarea completa: enunciado, fechas, archivos adjuntos, estado de mi entrega y retroalimentación.

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

Input Schema

NameRequiredDescriptionDefault
cursoNoId o nombre del curso para desambiguar (opcional)
tareaYesId de la tarea (o id de módulo de la URL view.php?id=) o parte de su nombre

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the load. It does usefully disclose the payload scope, including that results are personalized ('estado de mi entrega y retroalimentación'), which signals a user-scoped read. It says nothing about behavior when the id is ambiguous or not found, nor how the optional course parameter affects resolution.

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?

One front-loaded sentence listing the verb followed by the returned contents, with no filler. Nothing could be removed without losing information.

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 simple two-parameter read tool with no output schema, enumerating the returned fields compensates reasonably well for the absent return contract. The main remaining gap is what happens on ambiguous names or missing assignments, which would matter given that 'tarea' accepts partial names.

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 coverage is 100%, and the schema itself explains both 'tarea' (id, module id from view.php?id=, or partial name) and the optional 'curso' for disambiguation. The description adds no meaning beyond that, so the baseline 3 applies.

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 concrete verb ('Muestra') and resource ('tarea') and enumerates what the result contains (enunciado, fechas, adjuntos, estado de entrega, retroalimentación). The word 'completa' implicitly separates it from a listing tool like listar_tareas, though 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the enumeration of full detail suggests it is for inspecting one specific assignment rather than browsing. There is no explicit when-to-use, no mention of listar_tareas as the alternative for listing, and no stated preconditions.

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