Skip to main content
Glama
Sign In
flarum-mcp

flarum-mcp

by ReverserID
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search discussions

search_discussions

Search forum discussions by query to retrieve matching titles with ID, author, and tags. Controls result count from 1 to 50.

Instructions

Full-text search discussions on the forum. Returns matching titles with id, author, and tags.

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": {
      "query": "<query>"
    },
    "name": "search_discussions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1–50)
queryYesSearch text

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. The description says 'full-text search' but then 'Returns matching titles', which is ambiguous about whether it searches only titles or full content. No mention of read-only nature, order, pagination, or authentication requirements.

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

Conciseness4/5

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

Two concise sentences. Front-loaded with action and return info. Minimal waste.

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

Completeness3/5

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

Schema covers parameter details. No output schema. Description lacks clarity on search scope (titles vs full content) and does not mention pagination behavior. Adequate but with minor gaps.

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 covers both parameters with descriptions (query and limit). Description adds no additional semantics beyond the schema. Baseline 3 is appropriate.

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 it performs full-text search on discussions and specifies returned fields (title, id, author, tags). Distinguishes from siblings like discussions_by_tag which filters by tag, and recent_discussions which returns recent, not searchable.

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 on when to use this tool versus alternatives. It does not mention use cases or exclusions like 'use discussions_by_tag for tag-specific queries.' The agent must infer from sibling names.

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