Skip to main content
Glama
cameronrye

AT Protocol MCP Server

by cameronrye
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discover_communities

Read-only

Search for posts on a topic and cluster authors who interact with each other to reveal topic-based communities.

Instructions

Discover communities and groups of users around specific topics or interests by searching recent posts and clustering authors who interact with each other. Works without authentication; richer with auth. Use this instead of find_similar_users when you want topic-based community clusters rather than accounts structurally similar to a specific user. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesKeyword or phrase to search for (e.g. "climate", "web dev"). Used to retrieve relevant posts and identify active community clusters.
maxResultsNoMaximum number of communities to return (1–50, default 20).
minCommunitySizeNoMinimum number of distinct members required for a cluster to be reported as a community (minimum 2, default 5).
includeMetricsNoWhen true, includes a metrics object on each community with avgFollowerCount, totalPosts, and interconnectedness values (default true).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the operation completed successfully.
communitiesYesList of discovered communities sorted by size and engagement (descending).
insightsYesSummary observations about the discovered communities (e.g. total members, largest community).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / minCommunitySize / maximum
      Added value: +9007199254740991
  2. Changed5 schema fields changedv0.6.0
    • addedInput schema / properties / includeMetrics / description
      Added value: +"When true, includes a metrics object on each community with avgFollowerCount, totalPosts, and interconnectedness values (default true)."
    • addedInput schema / properties / maxResults / description
      Added value: +"Maximum number of communities to return (1–50, default 20)."
    • addedInput schema / properties / minCommunitySize / description
      Added value: +"Minimum number of distinct members required for a cluster to be reported as a community (minimum 2, default 5)."
    • addedInput schema / properties / topic / description
      Added value: +"Keyword or phrase to search for (e.g. \"climate\", \"web dev\"). Used to retrieve relevant posts and identify active community clusters."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "communities": {
+      "description": "List of discovered communities sorted by size and engagement (descending).",
+      "items": {
+        "properties": {
+          "activityLevel": {
+            "description": "Activity level based on average posts per member: high (>=3), medium (1.5–2.9), low (<1.5).",
+            "enum": [
+              "high",
+              "medium",
+              "low"
+            ],
+            "type": "string"
+          },
+          "coreMembers": {
+            "description": "Up to 10 most relevant members, sorted by relevance score descending.",
+            "items": {
+              "properties": {
+                "avatar": {
+                  "description": "Avatar URL, if set.",
+                  "type": "string"
+                },
+                "did": {
+                  "description": "DID of the member.",
+                  "type": "string"
+                },
+                "displayName": {
+                  "description": "Display name, if set.",
+                  "type": "string"
+                },
+                "followersCount": {
+                  "description": "Follower count.",
+                  "type": "number"
+                },
+                "handle": {
+                  "description": "Bluesky handle of the member.",
+                  "type": "string"
+                },
+                "postsCount": {
+                  "description": "Posts contributed to the topic in this search.",
+                  "type": "number"
+                },
+                "relevanceScore": {
+                  "description": "Relevance score based on engagement and post count.",
+                  "type": "number"
+                }
+              },
+              "required": [
+                "did",
+                "handle",
+                "followersCount",
+                "postsCount",
+                "relevanceScore"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "description": {
+            "description": "Auto-generated human-readable summary of the community.",
+            "type": "string"
+          },
+          "metrics": {
+            "description": "Optional metrics object; present when includeMetrics is true.",
+            "properties": {
+              "avgFollowerCount": {
+                "description": "Average follower count across all members.",
+                "type": "number"
+              },
+              "interconnectedness": {
+                "description": "Ratio of cross-member interactions to community size.",
+                "type": "number"
+              },
+              "totalPosts": {
+                "description": "Total posts by all community members on this topic.",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "name": {
+            "description": "Auto-generated name for the community (e.g. \"climate Community 1\").",
+            "type": "string"
+          },
+          "size": {
+            "description": "Number of distinct members in the community.",
+            "type": "number"
+          },
+          "topic": {
+            "description": "The topic keyword used to discover this community.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "topic",
+          "size",
+          "coreMembers",
+          "activityLevel",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "insights": {
+      "description": "Summary observations about the discovered communities (e.g. total members, largest community).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "success": {
+      "description": "Whether the operation completed successfully.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "communities",
+    "insights"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changedv0.3.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. First observedv0.2.1

TDQS

A4.7/5.0
Behavior5/5

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

Discloses the reading behavior (clustering posts/authors) which aligns with annotations (readOnlyHint). Adds context about authentication and rate limits, going beyond the annotations to inform the agent of constraints and richer functionality.

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 four concise sentences with no redundant information. Each sentence serves a distinct purpose: stating the primary function, authentication, differentiation from a sibling, and rate limiting. It is front-loaded with the core action.

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?

Given the presence of an output schema (no need to describe returns), the description covers the tool's behavior, authentication, rate limiting, and relationship to a sibling tool. It is complete for a tool of this complexity with good annotations.

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 description coverage is 100%, so the baseline is 3. The tool description does not add new parameter details beyond what the schema provides, but it provides overall context for how parameters ('topic') are used (searching posts and clustering authors), which is adequate.

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 discovers topic-based communities by searching posts and clustering interacting authors. It distinguishes itself from the sibling 'find_similar_users' by specifying when to use each, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly mentions authentication requirements ('Works without authentication; richer with auth'), provides a condition for use ('Use this instead of find_similar_users when you want topic-based community clusters'), and notes rate limiting ('Subject to per-tool rate limiting').

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