Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

avisos_y_foros

Read-only

Retrieves the latest notices and forum discussions for a course, listing notices first; specify a forum ID to focus on a single forum.

Instructions

Últimos avisos y discusiones de los foros de un ramo (los avisos primero). Usa foro_id para un solo foro.

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": {
      "ramo": "<ramo>"
    },
    "name": "avisos_y_foros"
  }
}

Input Schema

NameRequiredDescriptionDefault
ramoYes
limiteNo
foro_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 genuine behavioral context by stating the result ordering (announcements before discussions) and the per-forum filtering effect. It does not say how the limit splits across the two sources or how many items come from each, which matters for an aggregating tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler; the composed result and its ordering come first, the parameter hint second. Every clause carries information an agent can act on.

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?

An output schema exists, so return values need no explanation, and the required ramo plus the foro_id narrowing are covered. The remaining gap is how limite interacts with the two merged sources, but for a read-only aggregation tool of this complexity the definition is close to sufficient.

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 0%, so the description must carry parameter meaning and it only partially does: foro_id's effect (single forum) is explained, and 'últimos' hints at recency. 'limite' is never mentioned despite having a default of 10 and directly determining result volume, and 'ramo' is left entirely to inference.

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 specific resource (avisos y discusiones de foros) scoped to a ramo and states the merge order ('los avisos primero'), which lets an agent distinguish it from single-thread readers like leer_discusion. It stops short of naming that sibling or clarifying whether announcements come from a separate source, but the verb+resource is concrete.

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?

The clause 'Usa foro_id para un solo foro' tells the agent when to narrow to one forum, which is real usage guidance for that parameter. There is no explicit when-to-use versus siblings (e.g. leer_discusion for a full thread, contenido_ramo for materials) and no exclusions or prerequisites.

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