Skip to main content
Glama
Sign In
MCP for Flarum

MCP for Flarum

by linkrobins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Flarum troubleshooting & support-request guide

flarum_troubleshoot

Diagnose broken Flarum forums: apply safe first-aid, run php flarum info, find logs, interpret errors, and write a support request.

Instructions

A plain-language guide for forum ADMINS and non-developers to diagnose a broken or misbehaving Flarum forum and prepare a request for help (distinct from flarum_dev, which is for building extensions). Covers safe first-aid fixes, how to run php flarum info and find logs on their hosting, what common errors mean, and how to write a redacted support request and where to post it. Use it whenever a user describes a forum problem or asks how to get help, and pair it with the prepare-flarum-support-request prompt to assemble a report from a forum that still loads. Omit topic for the full guide, or pass one to narrow it.

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

Input Schema

NameRequiredDescriptionDefault
topicNoSection to return: first-aid, info, logs, common, report (or 'all' / omit for the full guide).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.2

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description bears the full burden. It transparently describes the tool as a guide covering safe fixes, commands, error interpretation, and report writing, with no hidden side effects. It does not mention limitations (e.g., if forum is inaccessible), but overall disclosure is good.

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?

The description is roughly three sentences but packs in audience, purpose, distinguishment, coverage, and usage pairing. It is front-loaded with key information. Could be slightly tighter but remains efficient and clear.

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

Completeness4/5

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

With no output schema, the description must explain what the guide covers. It does so thoroughly (first-aid, info, logs, common errors, how to write a support request) and mentions pairing with another tool. For a guide tool, this is adequately complete.

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?

There is only one parameter (topic) with enum values, and the schema already provides clear descriptions (100% coverage). The description adds minimal but useful context ('Section to return... or omit for full guide'), so it meets the baseline without exceeding it.

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 the tool is a plain-language guide for forum admins to diagnose broken Flarum forums and prepare support requests. It explicitly distinguishes itself from the sibling tool flarum_dev, which is for building extensions, ensuring no confusion.

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 description advises using the tool 'whenever a user describes a forum problem or asks how to get help' and suggests pairing with a related prompt. It implicitly excludes use for extension development via the sibling distinction, though it does not explicitly state when not to use.

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