Skip to main content
Glama

listar_tareas

Read-only

Lists upcoming, overdue, or completed assignments with subject and original due dates; use the task-reading tool for full deadlines and instructions.

Instructions

Consulta tareas, materia y fechas originales. Usa leer_tarea para la fecha completa y la consigna.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listar_tareas"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
estadoNoproximas
limiteNo
materia_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 covered. The description adds one genuinely useful trait beyond them: the dates returned here are partial ("fechas originales") and require a follow-up leer_tarea call. It omits pagination/cursor behavior and the default limit of 50, which matter for a paginated read.

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 the core capability first and the sibling routing second; nothing is padded. The first sentence is slightly telegraphic ("fechas originales" is left ambiguous), but no wording is wasted.

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 explained, and annotations cover safety. With four parameters at 0% schema coverage, though, the description should at least explain the estado values that define what the tool actually returns, and it does not.

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 carry the parameter burden, but it only implicitly gestures at "materia" (materia_id). The estado enum (proximas/vencidas/completadas), the cursor and the limite cap of 100 are never mentioned, leaving the most consequential filters 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 names a specific verb plus resource ("Consulta tareas") and lists what is surfaced (materia, fechas originales), and it explicitly separates this tool from leer_tarea. It stops short of calling the operation a paginated list, so scope is only implied.

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?

"Usa leer_tarea para la fecha completa y la consigna" gives an explicit alternative and the condition that selects it, which is exactly the routing an agent needs. No guidance is given about other list siblings (listar_materias, listar_archivos), but those are not close substitutes.

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