Skip to main content
Glama
GodisinHisHeaven

USCardForum MCP Server

get_notifications

Fetch notifications from USCardForum to check replies, mentions, likes, and topic updates. Requires authentication and supports filtering by recency, read status, and quantity.

Instructions

Fetch your notifications. REQUIRES AUTHENTICATION.

Args:
    since_id: Only get notifications newer than this ID (optional)
    only_unread: Only return unread notifications (default: False)
    limit: Maximum number to return (optional)

Must call login() first.

Returns a list of Notification objects with:
- id: Notification ID
- notification_type: Type of notification
- read: Whether read
- topic_id: Related topic
- post_number: Related post
- created_at: When created

Use to:
- Check for new replies to your posts
- See mentions and likes
- Track topic updates you're watching

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
since_idNoOnly get notifications newer than this ID
only_unreadNoOnly return unread notifications
limitNoMaximum number to return

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary MCP tool handler for 'get_notifications'. Decorated with @mcp.tool(), defines the input schema using Pydantic's Annotated and Field for parameters (since_id, only_unread, limit), includes detailed docstring, and implements the logic by delegating to the underlying client.get_notifications() method. This is the entrypoint for the MCP tool execution.
    @mcp.tool()
    def get_notifications(
        since_id: Annotated[
            int | None,
            Field(default=None, description="Only get notifications newer than this ID"),
        ] = None,
        only_unread: Annotated[
            bool,
            Field(default=False, description="Only return unread notifications"),
        ] = False,
        limit: Annotated[
            int | None,
            Field(default=None, description="Maximum number to return"),
        ] = None,
    ) -> list[Notification]:
        """
        Fetch your notifications. REQUIRES AUTHENTICATION.
    
        Args:
            since_id: Only get notifications newer than this ID (optional)
            only_unread: Only return unread notifications (default: False)
            limit: Maximum number to return (optional)
    
        Must call login() first.
    
        Returns a list of Notification objects with:
        - id: Notification ID
        - notification_type: Type of notification
        - read: Whether read
        - topic_id: Related topic
        - post_number: Related post
        - created_at: When created
    
        Use to:
        - Check for new replies to your posts
        - See mentions and likes
        - Track topic updates you're watching
        """
        return get_client().get_notifications(
            since_id=since_id, only_unread=only_unread, limit=limit
        )
  • Helper method in the Client class that wraps the AuthAPI.get_notifications() call. Directly invoked by the MCP tool handler via get_client().get_notifications().
    def get_notifications(
        self,
        since_id: int | None = None,
        only_unread: bool = False,
        limit: int | None = None,
    ) -> list[Notification]:
        """Fetch notifications (requires auth).
    
        Args:
            since_id: Only notifications after this ID
            only_unread: Only unread notifications
            limit: Maximum notifications to return
    
        Returns:
            List of notification objects
        """
        return self._auth.get_notifications(
            since_id=since_id, only_unread=only_unread, limit=limit
        )
  • Core helper implementation in AuthAPI class that performs the actual HTTP GET to /notifications.json, parses the JSON response into Notification objects, and applies client-side filtering based on since_id, only_unread, and limit parameters.
    def get_notifications(
        self,
        since_id: int | None = None,
        only_unread: bool = False,
        limit: int | None = None,
    ) -> list[Notification]:
        """Fetch notifications (requires auth).
    
        Args:
            since_id: Only notifications after this ID
            only_unread: Only unread notifications
            limit: Maximum notifications to return
    
        Returns:
            List of notification objects
        """
        self._require_auth()
        payload = self._get("/notifications.json")
        raw_notifications = payload.get("notifications", [])
    
        notifications = [Notification(**n) for n in raw_notifications]
    
        # Apply filters
        if since_id is not None:
            notifications = [n for n in notifications if n.id > since_id]
        if only_unread:
            notifications = [n for n in notifications if not n.read]
        if limit is not None:
            notifications = notifications[: max(0, int(limit))]
    
        return notifications
  • Re-export of the get_notifications tool from auth.py module, making it available in the server_tools namespace for import into the main server.py.
    from .auth import (
        login,
        get_current_session,
        get_notifications,
        bookmark_post,
        subscribe_topic,
    )
  • Import of get_notifications from server_tools into the main server entrypoint, exposing it to the MCP server runtime (likely auto-registered via decorator or introspection).
    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,
    )
Behavior4/5

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

With no annotations provided, the description carries full burden and does well: it discloses authentication requirement ('REQUIRES AUTHENTICATION'), specifies prerequisite action ('Must call login() first'), and describes return format. However, it doesn't mention rate limits, pagination behavior, or error conditions that would be helpful for a notification-fetching tool.

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, authentication requirement, parameters, returns, use cases). While slightly verbose with the parameter repetition, every sentence adds value. The front-loaded purpose statement is clear and followed by important constraints.

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 tool has an output schema (implied by the Returns section detailing Notification objects), the description provides excellent contextual completeness. It covers authentication requirements, parameter guidance, return format, and specific use cases - all necessary for a read-only data retrieval tool with authentication needs.

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 all three parameters. The description repeats the parameter information in the 'Args:' section but doesn't add meaningful semantic context beyond what's in the schema. 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 verb ('Fetch') and resource ('your notifications'), distinguishing it from siblings like get_user_actions or get_user_replies which focus on different data types. It explicitly identifies what resource is being retrieved.

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?

The description provides explicit usage guidance: 'Must call login() first' establishes a prerequisite, and the 'Use to:' section gives three concrete scenarios for when to use this tool (checking replies, seeing mentions/likes, tracking topic updates). This clearly distinguishes it from other notification-related tools that don't exist in the sibling list.

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