Skip to main content
Glama
Sign In
ufsc-moodle-mcp

ufsc-moodle-mcp

by jeanmartina
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Listar grupos, agrupamentos e regras mod_groupselect da disciplina

get_course_groups
Read-onlyIdempotent

Lists Moodle course groups with members, groupings, permissions, and group-select activity rules, plus a suggested next unique group name.

Instructions

Lista todos os grupos de uma disciplina no Moodle (core_group_get_course_groups), seus participantes atuais, agrupamentos (groupings), permissão moodle/course:managegroups, sugestão de próximo nome único e a configuração completa das atividades mod_groupselect (como agrupamento associado, limites mínimo/máximo de participantes, prazos e permissões de criação).

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

Input Schema

NameRequiredDescriptionDefault
courseIdNoID da disciplina no Moodle (resolvido automaticamente se activityCmid for informado).
activityCmidNoCourse module ID (cmid) opcional de uma atividade mod_groupselect (ex: 1569070) para inspecionar suas regras e verificar disponibilidade de cada grupo nela.
includeMembersNoSe true (padrão), inclui a lista confirmada de integrantes de cada grupo.
includeGroupSelectNoSe true (padrão), consulta automaticamente as configurações de mod_groupselect da disciplina.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine context that the tool is an aggregator (group data plus groupings plus mod_groupselect configuration), but it does not disclose costs, extra round-trips, or behavior when no groups exist.

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?

A single front-loaded sentence that opens with the primary action and then enumerates return payloads; every clause maps to real output. The enumeration is dense but not padded, and the main purpose is not buried.

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?

With no output schema, the description usefully enumerates what is returned (groups, participants, groupings, permission, next name, mod_groupselect config), which is exactly what an agent needs to decide to call it. Annotations carry the safety profile; only edge-case behavior is unstated.

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 coverage is 100%, so the schema already documents courseId, activityCmid, includeMembers and includeGroupSelect including defaults. The description reinforces what the output contains when includeGroupSelect is used but adds no syntax or format meaning beyond the schema; baseline 3 applies.

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 verb and resource (list all course groups) and enumerates the concrete payload it returns: members, groupings, managegroups permission, next unique-name suggestion, and mod_groupselect rules, backed by the underlying core_group_get_course_groups call. It is distinguishable from get_group_members (ranges beyond one group) but never explicitly contrasts itself with that sibling.

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 phrase 'lista todos os grupos de uma disciplina'; there is no explicit when-to-use, when-not, or pointer to alternatives like get_group_members or create_course_group. The optional activityCmid hint gives some contextual framing for inspecting mod_groupselect rules, but no routing guidance.

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

Deploy Server

Other Tools