Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

proximas_entregas

Read-only

Retrieves upcoming assignment and activity deadlines within a specified number of days, optionally filtered by course, and can include overdue items from the past two weeks.

Instructions

Entregas y actividades pendientes con fecha límite en los próximos dias días.

Con incluir_atrasadas también muestra las pendientes vencidas en las últimas 2 semanas. ramo filtra por un ramo.

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

Input Schema

NameRequiredDescriptionDefault
diasNo
ramoNo
incluir_atrasadasNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: that incluir_atrasadas extends the window backward two weeks into overdue items, which the schema alone never says. It omits result ordering, limits, or volume expectations, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core purpose and parameter modifiers afterward; backticks make the parameters easy to scan. The ramo sentence is tautological and could be dropped or made informative without losing anything.

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 the read-only annotation covers safety. Still, for a discovery tool with three undocumented parameters, the description leaves open how many items come back, whether results are sorted by deadline, and what a ramo value should be.

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 the parameter burden. It explains `dias` as the forward window and `incluir_atrasadas` as adding two weeks of overdue items, but '`ramo` filtra por un ramo' merely restates the parameter name without clarifying what a ramo identifier looks like or how it is obtained.

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 states a specific resource and scope: pending assignments and activities whose deadline falls within the next `dias` days. That is far more than a restatement of the name 'proximas_entregas', but it never contrasts itself with sibling tools such as ver_tarea or ver_notas, so the agent must infer which one to pick.

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 implied by the described output ('pending items due soon'), and the conditional behavior of incluir_atrasadas is spelled out. There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named for the case of inspecting a single item.

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