Skip to main content
Glama
Sign In
enauczanie-mcp

enauczanie-mcp

by Zambrzyckii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_discussion_posts

Retrieves all posts from a forum discussion by discussion ID, returning full text in oldest-first order.

Instructions

Return all posts of one forum discussion (discussion_id from get_forum_discussions), oldest first, full text.

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": {
      "discussion_id": "<discussion_id>"
    },
    "name": "get_discussion_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
discussion_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: results are ordered 'oldest first' (chronological thread order, not relevance), and text is returned 'full' rather than truncated. It does not mention pagination limits or permission requirements, which is the remaining gap for an unannotated tool.

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 sentence with no filler, front-loading the action and scope, then the parameter provenance, then the ordering/format guarantees. Every clause earns its place.

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

Completeness5/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 and no annotations, the description covers purpose, prerequisite, ordering, and content completeness — everything needed to invoke it correctly. Anything more would be redundant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema only says 'integer', so the description's note that the value comes from get_forum_discussions is genuine added meaning about provenance. It does not clarify whether the id is a course-scoped or global identifier, but the source tool reference resolves most ambiguity.

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?

Specific verb ('Return all posts') plus a precisely scoped resource ('one forum discussion'), and it explicitly distinguishes itself from the sibling get_forum_discussions, which lists discussions rather than posts. An agent can select between the two without opening either schema.

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?

The parenthetical '(discussion_id from get_forum_discussions)' states the prerequisite and the tool that supplies it, encoding a clear two-step workflow. It stops short of stating when not to use this tool, but for a single-purpose reader there is no plausible alternative to exclude.

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

Deploy Server

Other Tools