Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

vincular_carpeta

Idempotent

Links a Moodle course to its local folder and suggests candidate folders when none is provided, without creating directories.

Instructions

Vincula un ramo con su carpeta local (ruta absoluta o relativa a AULA_DIR_BASE).

Sin carpeta, solo sugiere carpetas candidatas. No crea carpetas.

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

Input Schema

NameRequiredDescriptionDefault
ramoYes
carpetaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Adds real behavioral context beyond the annotations: it explicitly states 'No crea carpetas' and that omitting `carpeta` degrades to a suggestion-only, non-mutating call — which usefully qualifies the write-ish readOnlyHint=false profile. It does not disclose where the link is persisted or what happens if the folder is later moved or deleted, so it stops short of full transparency for a mutating tool. No annotation contradiction: the description's mutation-plus-suggestion behavior is consistent with readOnlyHint=false and destructiveHint=false.

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?

Two short sentences with zero filler: the core action plus path rule first, then the fallback mode and the non-creation constraint. Front-loaded and easy to parse, though the parenthetical breaks the flow slightly.

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

Completeness5/5

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

For a two-parameter tool with an output schema (so return values need not be described) and annotations covering the safety profile, the description supplies the missing pieces: path resolution, the suggestion fallback, and the no-folder-creation guarantee. Nothing an agent needs to call it correctly is left out, aside from the minor `ramo` ambiguity.

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?

Schema description coverage is 0%, so the description carries the burden, and it explains the path semantics of `carpeta` (absolute or relative to AULA_DIR_BASE) and the meaning of omitting it. The `ramo` parameter is left uninterpreted — the agent must infer whether it is a name, slug, or id. Net: it adds substantial meaning but leaves one of two params unexplained.

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 and resource: linking a course ('ramo') to its local folder, with the path resolution rule (absolute or relative to AULA_DIR_BASE). The action is unambiguous, though it does not explicitly contrast itself with any sibling tool — the sibling list suggests no real overlap, so the risk is low.

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?

Gives a clear conditional: with `carpeta` the tool links, without it the tool only suggests candidate folders. That is genuine when-to-use guidance for the two modes. It omits prerequisites (e.g. local filesystem access, whether the course must already exist).

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