Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

listar_ramos

Read-only

Lists a student's Moodle courses, showing each course ID and its linked local folder, with an option to include past courses.

Instructions

Lista los ramos del estudiante (por defecto solo los vigentes), con su id y la carpeta local vinculada.

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

Input Schema

NameRequiredDescriptionDefault
incluir_pasadosNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 real behavioral context beyond that: the default result set excludes non-current courses, and each item includes a linked local folder, which is useful for an agent deciding whether to unbind or re-link folders.

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?

One front-loaded sentence with no filler; the default-scope constraint is stated immediately and the returned fields follow. Nothing could be removed without losing information.

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 not be detailed, and the annotations cover the safety profile. For a one-parameter read tool this is nearly complete; the only gap is not explicitly tying the default-state note to the incluir_pasados flag.

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

Parameters3/5

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

Schema description coverage is 0% for the single boolean incluir_pasados, so the description must compensate. Saying 'por defecto solo los vigentes' implies that something can widen the scope to past courses, but it never names or explains the parameter, leaving the agent to infer that the toggle is what changes the default.

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?

States a specific verb (Lista) and resource (los ramos del estudiante) and even names what each entry carries: su id y la carpeta local vinculada. It is clear about scope, though it does not distinguish itself from siblings like contenido_ramo or contactos_ramo, which could look like related per-course tools.

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 parenthetical 'por defecto solo los vigentes' implies a default filter and thus when to expect past courses, but there is no explicit guidance on when to use this versus other course-scoped tools. Usage is only implied, not stated.

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