Skip to main content
Glama
raidenrock

USCardForum MCP Server

by raidenrock

get_new_topics

Fetch recently created topics from USCardForum to discover new deals, questions, and discussions before they become popular.

Instructions

Fetch the latest/newest topics from USCardForum.

Returns recently created topics sorted by creation time (newest first).
These may have fewer replies but contain fresh information.

Use this to:
- Find newly posted deals or offers
- See fresh questions from the community
- Discover emerging discussions before they get popular

Args:
    page: Page number for pagination (0-indexed). Use page=1 to get more topics.

Returns a list of TopicSummary objects with:
- id: Topic ID
- title: Topic title
- posts_count: Number of posts
- created_at: When the topic was created
- category_id: Which forum section it's in

Tip: New topics with high view counts may indicate important news.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (0-indexed, default: 0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for get_new_topics. Decorated with @mcp.tool(), defines input schema via Annotated[Field], and implements logic by delegating to the forum client.
    @mcp.tool()
    def get_new_topics(
        page: Annotated[
            int | None,
            Field(default=None, description="Page number for pagination (0-indexed, default: 0)"),
        ] = None,
    ) -> list[TopicSummary]:
        """
        Fetch the latest/newest topics from USCardForum.
    
        Returns recently created topics sorted by creation time (newest first).
        These may have fewer replies but contain fresh information.
    
        Use this to:
        - Find newly posted deals or offers
        - See fresh questions from the community
        - Discover emerging discussions before they get popular
    
        Args:
            page: Page number for pagination (0-indexed). Use page=1 to get more topics.
    
        Returns a list of TopicSummary objects with:
        - id: Topic ID
        - title: Topic title
        - posts_count: Number of posts
        - created_at: When the topic was created
        - category_id: Which forum section it's in
    
        Tip: New topics with high view counts may indicate important news.
        """
        return get_client().get_new_topics(page=page)
  • Re-exports the get_new_topics tool from topics.py, making it available when importing from server_tools package. Importing here triggers the @mcp.tool() registration.
    from .topics import (
        get_all_topic_posts,
        get_hot_topics,
        get_new_topics,
        get_top_topics,
        get_topic_info,
        get_topic_posts,
    )
  • Imports and re-exports get_new_topics in the main server entrypoint, ensuring the tool is registered when the server starts.
    get_new_topics,
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by disclosing key behaviors: it describes the sorting order ('newest first'), notes that topics may have fewer replies, explains pagination behavior, and details the return structure. However, it doesn't mention potential rate limits or authentication requirements, which could be relevant for a forum API.

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 usage guidelines, parameter details, return values, and a helpful tip. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 (1 parameter, read-only operation), no annotations, and the presence of an output schema, the description is complete: it covers purpose, usage, parameter semantics, return values, and behavioral context, leaving no significant gaps for an agent to understand and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining the pagination logic ('0-indexed', 'Use page=1 to get more topics') and providing context about what 'page' represents in this specific tool, elevating it above the baseline.

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 tool's purpose with specific verbs ('fetch', 'returns') and resources ('latest/newest topics from USCardForum'), distinguishing it from siblings like get_hot_topics or get_top_topics by emphasizing recency and freshness rather than popularity or ranking.

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?

It provides explicit usage scenarios ('Find newly posted deals', 'See fresh questions', 'Discover emerging discussions') and includes a tip about high view counts, offering clear guidance on when to use this tool versus alternatives like search_forum or get_hot_topics for different types of content discovery.

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