ufsc-moodle-mcp

Listar tarefas/trabalhos da disciplina

get_assignments

Read-onlyIdempotent

Retrieve all assignments for a Moodle course, including instructions, downloadable attachments, group submission settings, deadlines, and maximum grades.

Instructions

Lista todas as tarefas (assignments) de uma disciplina, incluindo enunciado, anexos do enunciado (baixáveis via download_moodle_file), configuração de entrega em grupo (teamsubmission), prazos e nota máxima.

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_assignments"
  }
}

Input Schema

Name	Required	Description	Default
`courseId`	No	ID da disciplina no Moodle.

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 this as a read-only, idempotent, non-destructive, closed-world operation, so safety needs no explanation. The description adds valuable disclosure beyond that by enumerating what the response contains (statement text, statement attachments, teamsubmission setting, deadlines, maximum grade) and by pointing to download_moodle_file for the attachments. Only pagination/volume behavior is left unstated.

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?

One front-loaded sentence with no filler; each parenthetical (the English term, the download pointer, the teamsubmission field name) carries real information. Slightly dense but nothing is wasted.

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?

For a one-parameter read tool with no output schema, the description does the important work of listing the returned fields so an agent knows what it will get. Gaps are minor: no mention of empty-result behavior or whether results are ordered/paginated.

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?

There is a single parameter whose schema description already covers it at 100% ('ID da disciplina no Moodle'), and the description echoes the same idea ('de uma disciplina') without adding format or sourcing detail. With schema coverage this high, the baseline of 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?

States a specific verb ('Lista') and resource ('tarefas (assignments) de uma disciplina'), including the English term for disambiguation. It does not explicitly distinguish itself from the nearby sibling get_submissions, which also deals with assignment data, so an agent must infer the split from the enumerated return fields.

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 implied: call this to see the assignments of a course before retrieving submissions or grading. The description also gives a useful routing hint that attachments are fetched with download_moodle_file, but it never states when not to use this tool or how it relates to get_assignment_grading_overview / get_submissions.

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