Skip to main content
Glama

notificaciones

Fetches Moodle notification-bell alerts such as grades, feedback, forum messages, and assignment changes without marking them read; optionally limits results or returns only unread items.

Instructions

Notificaciones de la campana de Moodle: calificaciones publicadas, retroalimentación, mensajes de foros, cambios en tareas, etc. No las marca como leídas.

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

Input Schema

NameRequiredDescriptionDefault
limiteNo
solo_no_leidasNoMostrar solo las no leídas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden. It does disclose one important trait, that the call does not mark notifications as read, which is the key non-side-effect guarantee for a notification tool. However, it says nothing about ordering, recency window, pagination, or the shape of what is returned, leaving meaningful gaps.

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 compact sentences with the content scope front-loaded, followed immediately by the read-state caveat. The type enumeration is slightly listy but each item earns its place by clarifying what appears in the feed.

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 two-parameter read tool with no output schema and no annotations, the description covers what the tool returns conceptually and one behavioral guarantee, but omits parameter meaning and return/pagination behavior. It is adequate but incomplete relative to the total lack of structured support.

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 50%: solo_no_leidas is documented in the schema, while limite only has type/default/min/max without explanation. The description mentions neither parameter, adding no meaning beyond the schema, so it fails to compensate for the coverage gap.

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 concrete resource, the Moodle notification bell, and enumerates what flows through it: published grades, feedback, forum messages, and assignment changes. That enumeration distinguishes it from single-purpose siblings such as calificaciones or mensajes, though the action itself (fetch/list) remains implicit.

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: an agent can infer this is the aggregate notification feed, but the description never says when to prefer it over a specific sibling like calificaciones or mensajes, nor any prerequisites or exclusions. No explicit when-to-use or when-not guidance is provided.

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