LearningSuite MCP Server

learningsuite_list_community_forums

Retrieve community forums with optional area filter and pagination. Use this to list forums and get their details for community management.

Instructions

Get community forums

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

Input Schema

Name	Required	Description
`limit`	No	Maximum to return
`areaId`	No	Filter by area ID
`offset`	No	Offset for pagination

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.6/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get community forums', offering no information about read safety, pagination behavior, authentication, or response format. The description is virtually a restatement of the tool name and gives no behavioral detail.

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 concise sentence, front-loaded with the verb 'Get'. It is appropriately sized but so minimal that it essentially rephrases the tool name without earning its place. It lacks any additional context, making it borderline under-specified rather than genuinely concise.

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 tool has three optional parameters and no output schema, the description is incomplete. It does not explain what the response contains, how pagination works, the default limit, or how areaId filtering behaves. The description could easily be augmented with a few sentences about usage without sacrificing conciseness.

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 schema descriptions cover 100% of parameters, with each parameter having a brief explanation. The tool description itself adds no parameter semantics, but since schema coverage is high, baseline is 3. The schema already documents limit, areaId, and offset, so no deduction is needed.

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 clearly states the tool retrieves community forums, using a specific verb and resource. It distinguishes itself from siblings like list_community_areas and list_community_posts by naming 'forums', though it is quite terse and adds little beyond the tool name.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of use cases, alternatives, or exclusions, leaving the agent to infer from the name alone.

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

Deploy Server