Skip to main content
Glama
GodisinHisHeaven

USCardForum MCP Server

list_users_with_badge

Find community members who have earned a specific achievement badge on USCardForum. Use this tool to identify users with particular recognition levels or accomplishments.

Instructions

List all users who have earned a specific badge.

Args:
    badge_id: The numeric badge ID
    offset: Pagination offset (optional)

Returns a dictionary with user badge information.

Use to find community members with specific achievements
or recognition levels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
badge_idYesThe numeric badge ID
offsetNoPagination offset

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_users_with_badge'. Defines input schema using Pydantic Annotated fields and implements the logic by calling the client API.
    @mcp.tool()
    def list_users_with_badge(
        badge_id: Annotated[
            int,
            Field(description="The numeric badge ID"),
        ],
        offset: Annotated[
            int | None,
            Field(default=None, description="Pagination offset"),
        ] = None,
    ) -> dict[str, Any]:
        """
        List all users who have earned a specific badge.
    
        Args:
            badge_id: The numeric badge ID
            offset: Pagination offset (optional)
    
        Returns a dictionary with user badge information.
    
        Use to find community members with specific achievements
        or recognition levels.
        """
        return get_client().list_user_badges(badge_id, offset=offset)
  • Imports all MCP tools including 'list_users_with_badge' from server_tools, registering them via the @mcp.tool decorators when the server starts.
    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,
    )
  • Re-exports 'list_users_with_badge' from the users module, making it available for import in higher-level modules like server.py.
    from .users import (
        get_user_summary,
        get_user_topics,
        get_user_replies,
        get_user_actions,
        get_user_badges,
        get_user_following,
        get_user_followers,
        get_user_reactions,
        list_users_with_badge,
    )
  • Core API client method that performs the HTTP GET request to '/user_badges.json' to retrieve users holding a specific badge. Called by the MCP handler via the client proxy.
    def list_users_with_badge(
        self,
        badge_id: int,
        offset: int | None = None,
    ) -> dict[str, Any]:
        """List users with a specific badge.
    
        Args:
            badge_id: Badge ID
            offset: Optional pagination offset
    
        Returns:
            Raw API response with users
        """
        params_list: list[tuple[str, Any]] = [("badge_id", int(badge_id))]
        if offset is not None:
            params_list.append(("offset", int(offset)))
    
        return self._get("/user_badges.json", params=params_list)
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns a dictionary with user badge information and mentions pagination via the offset parameter, which adds useful behavioral context. However, it doesn't cover important aspects like rate limits, authentication requirements, error conditions, or the structure of the returned dictionary beyond the high-level mention.

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 purpose statement, parameter explanations, return information, and usage context in four concise sentences. Each sentence adds value, though the parameter explanations slightly duplicate schema information. It's appropriately sized for a tool with two parameters.

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 that there's an output schema (though not shown in the prompt), the description doesn't need to explain return values in detail. With no annotations, 100% schema coverage, and a clear purpose, the description provides adequate context for this read-only listing tool. The main gap is lack of behavioral details like authentication or error handling, but the core functionality is well-covered.

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 fully documents both parameters. The description repeats the parameter information from the schema ('badge_id: The numeric badge ID', 'offset: Pagination offset') without adding meaningful semantic context beyond what's in the structured fields. This meets the baseline for high schema coverage.

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 ('List all users who have earned a specific badge') and the resource ('users with badge'), distinguishing it from sibling tools like get_user_badges (which gets badges for a user) or get_user_summary (which provides general user info). The purpose is precise and unambiguous.

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?

The description provides clear context for when to use this tool ('Use to find community members with specific achievements or recognition levels'), which helps differentiate it from general user listing tools. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the siblings, though the purpose naturally implies alternatives like get_user_badges for different queries.

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

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