ufsc-moodle-mcp

Consultar participantes confirmados de um grupo

get_group_members

Read-onlyIdempotent

Retrieve a confirmed, up-to-date member list for a Moodle group, including member count, max capacity, remaining slots, and mod_groupselect availability.

Instructions

Retorna a lista atualizada e confirmada de integrantes de um grupo específico no Moodle, juntamente com contagem de membros, limite máximo configurado (maxMembers), vagas restantes e disponibilidade na atividade mod_groupselect.

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": {
      "groupId": "<groupId>"
    },
    "name": "get_group_members"
  }
}

Input Schema

Name	Required	Description
`groupId`	Yes	ID do grupo (groupId) no Moodle.
`courseId`	No	ID opcional da disciplina (validado contra o grupo quando informado).
`activityCmid`	No	Course module ID opcional (ex: mod_groupselect) para verificar disponibilidade e limite de vagas.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Nov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real value beyond that by saying the list is 'atualizada e confirmada' and that computed fields (member count, configured maxMembers, remaining slots, mod_groupselect availability) are included — information the agent cannot get from the annotations.

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 with no filler, and the core resource is stated first before the returned fields. Dense but readable; slightly overloaded by stacking four returned values in one clause.

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?

There is no output schema, so the description has to convey the return shape — and it does, listing members plus four derived fields. For a simple read-only single-group lookup this is close to complete; only pagination/empty-group behavior and an explicit pointer to how to obtain groupId are missing.

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 100%, so all three parameters (groupId required, courseId, activityCmid) are already documented with intent. The description only implicitly connects activityCmid to the availability/maxMembers output; it adds no format, validation or default detail beyond the schema, so 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?

Names a specific verb and resource ('Retorna a lista atualizada e confirmada de integrantes de um grupo específico no Moodle') and enumerates what comes back (contagem, maxMembers, vagas restantes, disponibilidade no mod_groupselect). It is clearly different from listing groups or students, though it never names a sibling to contrast with.

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 resource: 'use this to check who is in a group'. There is no explicit when-to-use or when-not-to-use guidance versus get_course_groups, get_students, or add_group_member, and no stated prerequisite such as needing a valid groupId from get_course_groups.

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