Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

leer_discusion

Read-only

Fetches complete messages from a Moodle forum discussion using an ID from notices and forums, enabling review of the full conversation.

Instructions

Mensajes completos de una discusión de foro (discusion_id viene de avisos_y_foros).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "discusion_id": "<discusion_id>"
    },
    "name": "leer_discusion"
  }
}

Input Schema

NameRequiredDescriptionDefault
discusion_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that it returns complete message bodies rather than summaries, which is useful scope information, but says nothing about ordering, pagination, or access restrictions; the existing output schema absorbs the return-value burden.

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?

One compact sentence with the key scope ('completos') front-loaded and the prerequisite tucked into a parenthetical. Nothing is wasted, though the fragment style omits an explicit action verb.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-parameter tool with an output schema and annotation coverage, the description supplies what an agent needs: what it returns and where the id comes from. Only pagination/ordering behavior is left unspecified and is likely captured by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only one parameter and 0% schema description coverage, the description compensates by explaining the origin of discusion_id (it comes from avisos_y_foros), which the bare 'integer' schema does not convey. Format details beyond that are minimal but the single param is effectively covered.

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 ('Mensajes completos de una discusión de foro') and stresses 'completos', distinguishing it from the listing tool avisos_y_foros. It lacks an explicit verb, but the resource and scope are unambiguous.

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?

The parenthetical 'discusion_id viene de avisos_y_foros' gives a clear prerequisite workflow: obtain the id from avisos_y_foros before calling this. It gives no explicit exclusions or when-not conditions, so it stops short of a 5.

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