Skip to main content
Glama
Sign In
LearningSuite MCP Server

LearningSuite MCP Server

by fabienbutz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

learningsuite_list_community_posts

Retrieve community posts from LearningSuite. Supports filtering by forum, limit, and offset for pagination.

Instructions

Get community posts

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": "learningsuite_list_community_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum to return
offsetNoOffset for pagination
forumIdNoFilter by forum ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'Get', implying a read operation, but does not mention pagination, filtering, return format, or any side effects. It adds no value beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence and is front-loaded, but it is under-specified rather than concise. It omits important contextual information such as pagination and filtering, making it less helpful than it could be.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description should explain return behavior, pagination, and filtering, but it does none of these. For a list tool with three optional parameters, this is insufficient context for an AI agent to use it correctly.

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?

The input schema fully describes all three parameters (limit, offset, forumId) with individual descriptions, achieving 100% coverage. The tool description adds no additional parameter meaning, so the baseline of 3 applies.

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

Purpose3/5

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

The description states 'Get community posts', which clearly identifies the action and resource, but it is minimal and essentially restates the tool name. It distinguishes from sibling tools like list_community_forums by the resource type, but provides no details on scope or behavior.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as list_community_forums or comment_on_post. There is no context for appropriate use cases, exclusions, or relationships to sibling tools.

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