Skip to main content
Glama
cameronrye

AT Protocol MCP Server

by cameronrye

find_similar_users

Discover users similar to a specific account by analyzing mutual followers, content topics, and engagement patterns.

Instructions

Find users similar to a given user based on their content, followers, and engagement patterns. Analyzes mutual followers, content topics, and engagement to identify similar accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorYes
maxResultsNo
minFollowerCountNo
includeMetricsNo
Behavior2/5

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

Lacks annotations, so description carries full burden. It mentions analysis of mutual followers and engagement but does not disclose read-only nature, auth requirements, or limitations. Behavioral traits beyond the basic method are missing.

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 sentences, front-loaded with purpose. Concise without being verbose, though additional detail could be included without harming conciseness.

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

Completeness2/5

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

Given lack of annotations, output schema, and 4 parameters with no schema descriptions, the description is insufficient. It does not explain output format, similarity algorithm, or how parameters affect results.

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

Parameters1/5

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

With 0% schema description coverage, description provides no additional meaning for parameters like maxResults, minFollowerCount, or includeMetrics. It vaguely references 'content, followers, and engagement' but does not connect to specific parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool finds users similar to a given user based on content, followers, and engagement patterns. It uses specific verb and resource, and by mentioning similarity rather than influence, it subtly differentiates from sibling find_influential_users.

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 explicit guidance on when to use this tool versus alternatives like find_influential_users or analyze_network. Does not mention any exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cameronrye/atproto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server