ufsc-moodle-mcp

Ler tópicos e postagens de um fórum

get_forum_discussions

Read-onlyIdempotent

List forum topics or read all messages in a specific discussion by providing a forum ID or discussion ID.

Instructions

Lista os tópicos/discussões de um fórum ou lê todas as postagens/respostas de uma discussão específica.

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

Input Schema

Name	Required	Description
`limit`	No	Número máximo de discussões retornadas (padrão: 20).
`forumId`	No	ID do fórum (obtido via get_forums) para listar seus tópicos.
`discussionId`	No	ID de uma discussão específica para ler todas as mensagens/respostas dentro dela.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Nov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that in discussion mode it returns ALL messages/replies, which is useful behavioral context, but it says nothing about pagination behavior, truncation, or ordering of results.

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?

A single well-formed sentence covering both operating modes with no filler. The dual-mode framing is front-loaded and easy to parse.

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

Completeness3/5

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

For a 3-parameter read tool with no output schema, the description covers what the tool does but not what the response contains (discussion fields, post authors, timestamps) or how results are ordered or paginated. Adequate but leaves gaps an agent would want closed given the absence of an output schema.

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 (limit, forumId, discussionId) are already documented in the schema, including the default of 20 and the pointer to get_forums. The description restates the meaning of forumId and discussionId but adds no syntax or format detail beyond what the schema provides, 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 and resource for both modes: listing topics/discussions of a forum, or reading all posts/replies of a specific discussion. An agent can tell this apart from get_forums (which lists the forums themselves) and post_forum_discussion, though the description does not name those siblings explicitly.

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: the two modes are stated, so an agent can infer that passing forumId lists topics while passing discussionId reads posts. There is no explicit when-to-use guidance, no statement of prerequisites, and no routing to alternatives such as get_forums for discovering forum IDs.

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