Skip to main content
Glama
enauczanie-mcp

enauczanie-mcp

by Zambrzyckii

get_forum_discussions

List a course’s forum discussions newest first, optionally narrowed to one forum, with each thread’s first post so students can scan announcements and identify discussions to follow.

Instructions

List the latest discussions of a course's forums (type news = teacher announcements), newest first, each with its first post. forum_module_id (from get_course_contents) narrows to one forum; get_discussion_posts gives replies.

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": {
      "course_id": "<course_id>"
    },
    "name": "get_forum_discussions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
course_idYes
forum_module_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose ordering, the first-post inclusion, the news-type meaning, and filter behavior, but says nothing about permissions/visibility rules, pagination, or what happens when forum_module_id is omitted beyond 'all forums'.

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 dense sentences with zero filler; scope, ordering, and return shape come first, with the parameter hint and sibling routing after. Every clause earns its place.

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 annotations or output schema, the description does the heavy lifting well: it defines ordering, return payload, and the filter. It falls short only on limit/pagination semantics, which matters for a listing tool.

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 0%, so the description must compensate. It explains forum_module_id well (including its source) and by implication course_id, but never addresses the limit parameter — its default of 10 or whether it caps total results or per-forum results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list forum discussions for a course), its ordering (newest first), and its payload (each with its first post). A parenthetical also decodes the 'news' type, so the resource is fully characterized.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes replies to get_discussion_posts and tells the agent where forum_module_id comes from (get_course_contents). It lacks an explicit 'when not to use / when another tool is better' clause for the general-browsing case, but the sibling routing is clear.

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