Skip to main content
Glama
rhettlong

USCardForum MCP Server

by rhettlong

get_notifications

Retrieve user notifications from USCardForum to monitor replies, mentions, likes, and watched topic updates. Requires authentication.

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

  • Primary MCP tool handler for 'get_notifications'. Decorated with @mcp.tool(), defines input parameters with descriptions (serving as input schema), and implements logic by calling the client method.
    @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
        )
  • Pydantic BaseModel defining the structure of a Notification object, used as the return type (list[Notification]) for the tool.
    class Notification(BaseModel):
        """A user notification."""
    
        id: int = Field(..., description="Notification ID")
        notification_type: int = Field(..., description="Type of notification")
        read: bool = Field(False, description="Whether read")
        created_at: datetime | None = Field(None, description="When created")
        topic_id: int | None = Field(None, description="Related topic ID")
        post_number: int | None = Field(None, description="Related post number")
        slug: str | None = Field(None, description="Topic slug")
        data: dict[str, Any] = Field(default_factory=dict, description="Extra data")
    
        class Config:
            extra = "ignore"
  • Client class method that wraps the AuthAPI.get_notifications() call, providing a high-level interface used by the tool handler.
    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
        )
  • Import of get_notifications from auth.py into the server_tools package __init__, making it available for import in server.py and exposing it as part of the tools package.
    from .auth import (
        login,
        get_current_session,
        get_notifications,
  • Import of get_notifications in the main server entrypoint, ensuring the tool is loaded when the server starts (tools auto-register via decorators).
    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,
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 by disclosing authentication requirements ('REQUIRES AUTHENTICATION', 'Must call login() first'), return format details, and filtering behavior. However, it doesn't mention rate limits, pagination, or error conditions, which 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 warning, parameters, returns, use cases). It's appropriately sized at 12 sentences, though the 'Args' section duplicates schema information and could be more concise. Most sentences earn their place by providing distinct value.

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's moderate complexity, 100% schema coverage, and presence of an output schema (implied by the detailed return description), the description is complete enough. It covers authentication, parameters, return format, and use cases without needing to explain return values since the output schema handles that.

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 all three parameters completely. The description repeats parameter information in the 'Args' section but doesn't add meaningful context beyond what's in the schema (e.g., typical ID ranges, practical limit values). 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 your notifications') and resource ('notifications'), distinguishing it from siblings like get_user_actions or get_user_replies. It explicitly mentions what notifications contain (replies, mentions, likes, topic updates), which helps differentiate its purpose from other user-related tools.

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 guidance on when to use this tool ('Check for new replies to your posts', 'See mentions and likes', 'Track topic updates you're watching') and includes a crucial prerequisite ('Must call login() first'). It also distinguishes usage from other notification-related tools by specifying the scope (personal notifications only).

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

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