Skip to main content
Glama
raidenrock

USCardForum MCP Server

by raidenrock

get_user_followers

Fetch followers for a USCardForum user to analyze community influence and engagement patterns through paginated results.

Instructions

Fetch the list of users following a specific user.

Args:
    username: The user's handle
    page: Page number for pagination (optional)

Returns a FollowList object with:
- users: List of FollowUser objects
- total_count: Total followers

A high follower count often indicates an influential
or helpful community member.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesThe user's handle
pageNoPage number for pagination

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
usersNoUser list
total_countNoTotal users

Implementation Reference

  • The MCP tool handler for 'get_user_followers'. Decorated with @mcp.tool(), defines input schema via Annotated Fields, output as FollowList, and delegates to client implementation.
    @mcp.tool()
    def get_user_followers(
        username: Annotated[
            str,
            Field(description="The user's handle"),
        ],
        page: Annotated[
            int | None,
            Field(default=None, description="Page number for pagination"),
        ] = None,
    ) -> FollowList:
        """
        Fetch the list of users following a specific user.
    
        Args:
            username: The user's handle
            page: Page number for pagination (optional)
    
        Returns a FollowList object with:
        - users: List of FollowUser objects
        - total_count: Total followers
    
        A high follower count often indicates an influential
        or helpful community member.
        """
        return get_client().get_user_followers(username, page=page)
  • Pydantic BaseModel defining the output structure (FollowList) returned by the get_user_followers tool.
    class FollowList(BaseModel):
        """List of followed/following users."""
    
        users: list[FollowUser] = Field(default_factory=list, description="User list")
        total_count: int = Field(0, description="Total users")
    
        class Config:
            extra = "ignore"
  • Import statement in server_tools __init__.py that exposes the get_user_followers tool from the users module, facilitating its registration in the MCP server.
    from .users import (
        get_user_actions,
        get_user_badges,
        get_user_followers,
        get_user_following,
        get_user_reactions,
        get_user_replies,
        get_user_summary,
        get_user_topics,
        list_users_with_badge,
    )
  • Import of all server tools including get_user_followers in the main server.py entrypoint, ensuring tool registration upon module load.
    from uscardforum.server_tools import (
        analyze_user,
        bookmark_post,
        compare_cards,
        find_data_points,
        get_all_topic_posts,
        get_categories,
        get_current_session,
        get_hot_topics,
        get_new_topics,
        get_notifications,
        get_top_topics,
        get_topic_info,
        get_topic_posts,
        get_user_actions,
        get_user_badges,
        get_user_followers,
        get_user_following,
        get_user_reactions,
        get_user_replies,
        get_user_summary,
        get_user_topics,
        list_users_with_badge,
        login,
        research_topic,
        resource_categories,
        resource_hot_topics,
        resource_new_topics,
        search_forum,
        subscribe_topic,
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions pagination and the return structure, but fails to disclose critical behavioral traits like authentication requirements, rate limits, error conditions (e.g., invalid username), or whether the data is real-time or cached. For a read operation with no annotation coverage, this leaves significant gaps.

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 well-structured with clear sections (purpose, args, returns, note) and front-loaded the core functionality. However, the final sentence about 'high follower count' is somewhat tangential and doesn't directly aid tool invocation, slightly reducing efficiency.

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?

Given the tool's moderate complexity (2 parameters, read-only operation), the description covers purpose, parameters, and return values adequately, especially with an output schema implied by the 'Returns' section. However, it lacks context on authentication, errors, or performance limits, which are important for a user-facing API tool.

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 schema already documents both parameters ('username' and 'page') fully. The description repeats the parameter info without adding meaningful context beyond what's in the schema, such as format examples for 'username' or default pagination behavior. Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Fetch the list of users following a specific user'), identifies the resource ('users following a specific user'), and distinguishes it from siblings like 'get_user_following' (which fetches users being followed) and 'get_user_summary' (which provides general user info). The verb 'fetch' is precise and the scope is well-defined.

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

Usage Guidelines3/5

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

The description implies usage when needing follower lists for a user, but provides no explicit guidance on when to use this tool versus alternatives like 'get_user_summary' (which might include follower count) or 'get_user_following'. It lacks clear exclusions or prerequisites, such as whether the user must exist or be public.

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/raidenrock/uscardforum-mcp'

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