Skip to main content
Glama

mensajes

Fetch Moodle message conversations with teachers or classmates and show each thread's latest message, with an optional result limit.

Instructions

Conversaciones de la mensajería de Moodle (mensajes de profesores o compañeros) con su último mensaje.

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

Input Schema

NameRequiredDescriptionDefault
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one useful trait — each conversation is returned with only its last message — but says nothing about read-only nature, ordering, pagination beyond the limit, or whether full message history is retrievable.

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?

A single compact sentence with the key qualifier ('con su último mensaje') placed where it matters. Nothing is padded, though brevity here reflects under-specification rather than discipline.

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 read tool with one optional parameter and no output schema, the description covers the core return concept, but omits the limit semantics, ordering, and scope (all conversations vs. recent) that an agent needs to call it confidently.

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?

The single parameter 'limite' has 0% description coverage and the description never mentions it, so the agent gets no explanation of what is being capped (number of conversations? messages?) or that a default of 10 applies. The schema carries bounds but the description adds no meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Conversaciones de la mensajería de Moodle') and clarifies its content ('con su último mensaje'), which tells an agent what data comes back. However, there is no verb (list? fetch? search?) and no differentiation from siblings like 'notificaciones' or 'anuncios', so the exact operation remains implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance is given, and no alternatives are mentioned. An agent cannot tell from the text whether this should be preferred over 'notificaciones' for unread alerts or 'ver_discusion' for course forum content.

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