USCardForum MCP Server

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

Name	Required	Description	Default
`page`	No	Page number for pagination (0-indexed, default: 0)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 30, 2025

TDQS

A4.7/5.0

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 of behavioral disclosure. It effectively describes key behaviors: it's a read operation (implied by 'fetch' and 'returns'), returns sorted data (newest first), and mentions pagination. However, it lacks details on rate limits, error handling, or authentication needs, which would be beneficial 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, starting with the core purpose, followed by usage guidelines, args, returns, and a tip. Every sentence adds value without redundancy, and it efficiently conveys necessary information in a compact format.

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 low complexity (1 optional parameter), 100% schema coverage, and the presence of an output schema (implied by the returns description), the description is complete. It covers purpose, usage, parameters, and return values adequately, leaving no significant gaps for an AI 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?

The schema description coverage is 100%, so the schema already documents the 'page' parameter. The description adds value by explaining pagination semantics ('0-indexed', 'Use page=1 to get more topics') and providing practical usage context, though it doesn't introduce new parameters or details beyond the schema's scope.

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 resource ('latest/newest topics from USCardForum'), distinguishing it from siblings like get_hot_topics or get_top_topics by emphasizing recency and freshness. It explicitly mentions sorting by creation time and that topics may have fewer replies, which differentiates it from tools focused on popularity or engagement.

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 scenarios with bullet points (e.g., 'Find newly posted deals or offers', 'See fresh questions from the community'), and the 'Tip' section offers additional context on when topics might be important. It implicitly distinguishes from siblings by focusing on newness rather than hotness or top topics, though it doesn't explicitly name alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.