Skip to main content
Glama

Lemmy

by io.github.pipeworx-io

Community

community
Read-onlyIdempotent

Fetch metadata for a specific Lemmy community by name (e.g. "asklemmy") or numeric id from the specified instance. Returns description, icon, subscriber count, and moderators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNo
name_or_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countsNoCommunity statistics (subscribers, posts, comments)
communityNoCommunity object with id, name, title, description
moderatorsNoList of community moderators

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name_or_id": "asklemmy@lemmy.world"
+  },
+  {
+    "instance": "lemmy.world",
+    "name_or_id": "12345"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Response from Lemmy API /community endpoint",
+  "properties": {
+    "community": {
+      "description": "Community object with id, name, title, description",
+      "type": "object"
+    },
+    "counts": {
+      "description": "Community statistics (subscribers, posts, comments)",
+      "type": "object"
+    },
+    "moderators": {
+      "description": "List of community moderators",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish read-only and idempotent behavior. The description adds value by stating what the tool returns (description, icon, subscriber count, moderators) and clarifying it fetches from a specified instance. It does not mention error cases, but the added context is sufficient for a simple read operation.

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?

The description is a single, well-structured sentence that front-loads the purpose, includes examples, and summarizes return fields. Every word contributes meaning with no fluff.

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

Completeness5/5

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

The tool is low-complexity: it fetches metadata for one community. The description covers purpose, input semantics, and key output fields, while annotations cover safety. The output schema exists, so the description is complete enough for an agent to invoke and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no parameter descriptions, so the description carries the full burden. It clearly explains that name_or_id can be a community name like 'asklemmy' or a numeric id, and that instance is the source instance. The schema examples reinforce this, making the parameter semantics unambiguous.

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 uses a specific verb ('Fetch metadata') and clearly identifies the resource: a specific Lemmy community by name or numeric id from a specified instance. This distinguishes it from the sibling 'communities' tool by focusing on a single community's metadata.

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?

It provides clear context for when to use the tool (fetching a specific community's metadata) and gives input format examples. It does not explicitly exclude alternatives like 'communities' for listing, but the singular/plural distinction strongly implies the appropriate use case.

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

All Lemmy toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all answer factual questions, while bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_fill_risk all analyze prediction markets. The Lemmy tools are distinct from the Pipeworx tools, but within each cluster an agent could easily select the wrong tool despite lengthy descriptions.

Naming Consistency2/5

Naming conventions are mixed: single nouns (post, community, site), verb_noun patterns (list_subscriptions, resolve_entity, generate_llms_txt), and ad-hoc names (ask_pipeworx, forget, recall). There is no consistent verb_noun or noun-only pattern across the set, making it hard to predict tool names.

Tool Count2/5

38 tools is excessive for a server named 'Lemmy' where only 7 tools (comments, communities, community, post, posts, search, site) actually relate to Lemmy. The vast majority of tools belong to an unrelated Pipeworx data platform, creating a severe scope mismatch and making the server feel bloated and unfocused.

Completeness2/5

For the Lemmy domain, the tools cover read-only browsing (list posts, view post, list communities, fetch community, comments, search, site metadata) but completely lack write operations like posting, commenting, voting, or moderation. The Pipeworx tools are extensive but do not compensate for the primary domain's gaps since the server is ostensibly about Lemmy.

Resources