Skip to main content
Glama

proximos_vencimientos

Retrieve upcoming and overdue Moodle activities, including assignments, quizzes, and forums, within a configurable day range to set reminders and track deadlines.

Instructions

Línea de tiempo: actividades con fecha de entrega próxima o vencida (tareas, cuestionarios, foros…). Úsala para recordatorios.

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

Input Schema

NameRequiredDescriptionDefault
diasNoCuántos días hacia adelante mirar
incluir_vencidasNoIncluir actividades vencidas de los últimos 7 días

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations the description carries the full burden. It does disclose the two windows of data returned (upcoming deadlines and recently overdue items) and the type of items, but says nothing about scope across courses, ordering, result size, or whether it is a pure 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, front-loaded with the resource definition and the item types, with no filler. The reminder sentence is brief but functional rather than wasteful.

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?

For a simple two-optional-parameter read tool with no output schema, the description is minimally adequate: it conveys what kind of items come back. It omits scope (all enrolled courses?) and ordering of the timeline, which matter for an aggregated deadline view.

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 100% (dias and incluir_vencidas are documented in the schema), so baseline 3 applies. The description's 'próxima o vencida' loosely echoes incluir_vencidas but adds no format, bounds, or default detail beyond the schema.

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?

Names the resource concretely ('línea de tiempo: actividades con fecha de entrega próxima o vencida') and enumerates the covered item types (tareas, cuestionarios, foros), which distinguishes it from the single-type siblings like listar_tareas or cuestionarios. It is a noun phrase rather than an explicit verb, so it just misses the top mark.

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?

'Úsala para recordatorios' gives a one-phrase use case but no when-not guidance and no named alternative (e.g., listar_tareas for a full task list). Usage is implied rather than spelled out.

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