4pda-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOURPDA_MIN_INTERVAL | No | Minimum interval between requests to 4PDA in seconds. Defaults to 1.0 (1 request per second), providing a 2x safety margin below the confirmed-safe 2 requests per second rate. If a 429 rate limit is encountered, the server applies a cooldown and returns a rate_limited payload. | 1.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_forumsA | List 4PDA forum categories/subforums. With no forum_id, returns the top-level categories (the forum tree roots). With a forum_id, returns that forum's subforums and a summary of its topics. IDs are 4PDA forum IDs. On rate limit, returns a 'rate_limited' payload with retry_after_seconds and retry_at_utc instead of an error — wait that long before calling again. |
| list_topicsA | List topics in a 4PDA forum (lofi version): id, title, reply count, is_important (pinned/important topics are prefixed with (!) on the site). On rate limit, returns a 'rate_limited' payload with retry_after_seconds and retry_at_utc instead of an error — wait that long before calling again. |
| list_postsA | List posts on a page of a 4PDA topic (lofi version), with author, date and HTML body. Internal links to the full version are rewritten to their lofi equivalent where one exists. The pinned header post repeats on every page on the site; it is dropped on page >= 2. Pages are 1-indexed; each page has 20 posts. On rate limit, returns a 'rate_limited' payload with retry_after_seconds and retry_at_utc instead of an error — wait that long before calling again. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool maps clearly to a different level of the forum hierarchy: forums, topics, and posts. There is minor overlap between list_forums with a forum_id and list_topics, since the former includes a topic summary, but the descriptions make the intended roles distinguishable.
All three tools follow the exact same list_<resource> pattern: list_forums, list_topics, list_posts. This is completely predictable and makes the toolset easy to navigate.
Three tools is an appropriate, lean size for a read-only forum browsing server. Each tool corresponds to a necessary step in the navigation flow: pick a forum, pick a topic, read posts.
The core forum traversal path is complete: forums lead to topics, and topics lead to posts. The main gap is the lack of a search tool or topic detail view, but these are reasonable omissions for a minimal browsing-focused server.