Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

contenido_ramo

Read-only

Retrieves course sections and resources—including resource IDs, types, names, and file sizes—to inspect the available materials and structure of a Moodle course.

Instructions

Secciones y recursos de un ramo (id de recurso, tipo, nombre y archivos con su tamaño).

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

Input Schema

NameRequiredDescriptionDefault
ramoYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only what the payload contains (sections, resources, files with sizes), which the output schema already carries, and says nothing about scope, permissions, or whether the whole course is returned at once.

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 short sentence with no filler, and the key resource is front-loaded. The parenthetical field list is arguably redundant given the output schema, which keeps it from a 5.

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

Completeness2/5

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

Because an output schema exists, the return-value description is not strictly needed, and the real gaps are elsewhere: the required 'ramo' argument is undefined and there is no usage context. For a tool that is the entry point into course materials, the definition is too thin.

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 required parameter 'ramo' has 0% schema description coverage, so the schema provides no meaning at all. The description mentions 'ramo' but never explains whether it is an id, a code, or a name, leaving the only input undocumented in both places.

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 set — the sections and resources of a course ('ramo'), including resource id, type, name and file sizes. An agent can tell this is a course-content inventory tool, distinct from siblings like ver_notas or descargar_material. It is a noun phrase with no verb, so it stops short of full specificity.

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?

There is no when-to-use guidance at all: nothing says this is the discovery step before leer_material or descargar_material, and no conditions or exclusions are given. The agent must infer the tool's role from the noun phrase alone.

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