Skip to main content
Glama
hmumixaM

USCardForum MCP Server

by hmumixaM

list_users_with_badge

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

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 function for 'list_users_with_badge'. Includes input schema definitions via Pydantic Annotated Fields. Executes by calling the client's list_user_badges method.
    @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)
  • Underlying API implementation in UsersAPI class that fetches users with a specific badge via the forum's /user_badges.json endpoint.
    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)
  • Main server entrypoint imports the list_users_with_badge tool (line 37 within the block), registering it for the MCP server via the @mcp.tool() decorator.
    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,
  • Package-level import of list_users_with_badge (line 46) from users.py, making it available for import in server.py.
        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,
    )
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 of behavioral disclosure. It mentions pagination via 'offset' and returns 'a dictionary with user badge information', which adds some context beyond the schema. However, it lacks details on permissions, rate limits, or what specific information the dictionary contains, leaving gaps for a tool with no annotations.

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 well-structured and front-loaded with the core purpose, followed by parameter details and usage guidelines. Every sentence earns its place: the first states the action, the second and third explain parameters, the fourth describes returns, and the fifth provides usage context, with no wasted words.

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, no annotations, but with output schema), the description is mostly complete. It covers purpose, parameters, returns, and usage, but lacks behavioral details like permissions or rate limits. The presence of an output schema reduces the need to explain return values, but more context would enhance completeness for a tool with no 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 schema already documents both parameters thoroughly. The description repeats 'badge_id: The numeric badge ID' and 'offset: Pagination offset (optional)', adding no extra meaning beyond the schema. This meets the baseline of 3 when schema coverage is high, but no additional value is provided.

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 verb 'List' and resource 'users who have earned a specific badge', making the purpose specific and actionable. It distinguishes from siblings like 'get_user_badges' (which gets badges for a user) by focusing on users for a badge, establishing clear differentiation.

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 explicit usage context: 'Use to find community members with specific achievements or recognition levels', which clearly indicates when this tool is appropriate. However, it does not specify when not to use it or name alternatives among siblings, such as 'get_user_badges' for a different perspective.

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/hmumixaM/uscardforum-mcp4'

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