ufsc-moodle-mcp

Listar tópicos, materiais e atividades da disciplina

get_course_contents

Read-onlyIdempotent

Retrieve a Moodle course's sections, materials, and activities—including files, links, assignments, forums, and quizzes—by course ID, with an optional section filter.

Instructions

Retorna todas as seções/tópicos, materiais (arquivos PDF, slides, links) e atividades (tarefas, fóruns, questionários) de uma disciplina. As URLs de arquivos retornadas podem ser baixadas via download_moodle_file ou lidas via read_moodle_file.

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

Input Schema

Name	Required	Description	Default
`courseId`	No	ID da disciplina no Moodle (use get_courses para descobrir).
`sectionNumber`	No	Filtra apenas uma seção específica pelo número da seção (0, 1, 2...).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Nov 7, 2026

TDQS

A3.8/5.0

Behavior4/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 safety is covered. Beyond that, the description discloses what kinds of entities come back and, importantly, that file URLs are returned and are meant to be consumed by two specific sibling tools. It does not mention response size, pagination, or performance on large courses, which is the main remaining gap.

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?

Two sentences, front-loaded with the primary result and followed by the actionable follow-up routing. Every clause earns its place and nothing is repeated from structured fields.

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 carries the burden of describing the return shape, which it does by enumerating sections, materials and activities. It also covers the follow-up path for returned URLs. Missing only volume/pagination expectations for large courses, which matters for an unbounded listing tool with both parameters optional.

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%: courseId's origin (use get_courses) and sectionNumber's 0-based numbering are already documented in the schema. The description adds no syntax or behavioral detail about the parameters, so the 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 ('Retorna') and enumerates the resources returned: sections/topics, materials (PDF, slides, links) and activities (assignments, forums, quizzes). This is far more informative than the title alone. It stops short of distinguishing itself from granular siblings like get_assignments or get_forums, leaving the agent to infer whether the aggregate listing replaces or precedes them.

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 by the purpose: call it to get a course's structural overview. The description also gives downstream routing, telling the agent to use download_moodle_file or read_moodle_file on the returned URLs. However, it does not state when NOT to use it or when a narrower sibling such as get_assignments should be preferred.

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