Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

contactos_ramo

Read-only

Retrieves the professors and teaching assistants for a course, including each person's role and email when Moodle makes it visible.

Instructions

Profesores y ayudantes de un ramo, con su rol y correo (si Moodle lo deja visible).

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

Input Schema

NameRequiredDescriptionDefault
ramoYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 value beyond that by disclosing that each contact carries a role and that the email is conditionally present depending on Moodle visibility settings — a non-obvious data-quality caveat the agent would otherwise be surprised by.

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; even the parenthetical caveat about Moodle visibility earns its place by qualifying the return data.

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?

An output schema exists, so return structure needn't be explained, and the read-only nature is covered by annotations. What is missing for a one-parameter lookup tool is the identifier convention for ramo, which is the only thing that can make the call fail.

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 ramo has 0% schema description coverage, so the description carries the full burden, and it only repeats the word 'ramo' without clarifying whether the value is a course ID, code, or name, or how to obtain it (e.g., via listar_ramos). That ambiguity directly affects whether the call succeeds.

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 (profesores y ayudantes de un ramo) and the fields returned (rol, correo), which is enough to distinguish it from content-oriented siblings like contenido_ramo or leer_material. It stops short of explicitly naming which sibling to use instead, so it lands just below the top band.

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?

Usage is only implied by the noun phrase itself: an agent can infer it is used when it needs the people teaching a course. There is no statement of when to prefer it over other course-scoped tools, no prerequisites, and no exclusion of cases.

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