Skip to main content
Glama
Sign In
flarum-mcp

flarum-mcp

by ReverserID
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Recent discussions

recent_discussions

Retrieve a list of recently active discussions from the forum, with an optional limit to control the number of results.

Instructions

List the most recently active discussions on the forum.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1–50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, and the description only says 'most recently active' without defining what constitutes 'active' (e.g., last reply, creation date, or activity score). It does not disclose whether the tool is read-only or safe, nor any potential side effects. The agent is left guessing the exact behavior.

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, concise sentence that imparts the core purpose with zero wasted words. It is appropriately front-loaded.

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 no output schema and no annotations, the description should compensate. It fails to describe what the output contains (e.g., titles, IDs, timestamps), whether results are paginated, or how 'recent' is ordered. For a simple tool, this is insufficient for an agent to fully understand the return value.

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 covers 100% of parameters (only 'limit') with a clear description. The tool description adds no further meaning beyond the schema, so baseline 3 applies.

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?

The description clearly states 'List the most recently active discussions on the forum,' which uses a specific verb ('List') and resource ('discussions'). It naturally distinguishes from sibling tools like 'search_discussions' or 'discussions_by_tag' which imply filtering, whereas this simply lists recent activity.

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 explicit guidance on when to use this tool over siblings. For example, it does not clarify that this is for browsing vs. searching, nor does it mention scenarios where 'search_discussions' or 'discussions_by_tag' would be more appropriate. The usage context is entirely implied.

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