USCardForum MCP Server

subscribe_topic

Set notification preferences for USCardForum topics to control when you receive updates, from muting to watching all posts.

Instructions

Set your notification level for a topic. REQUIRES AUTHENTICATION.

Args:
    topic_id: The topic ID to subscribe to
    level: Notification level:
        - 0: Muted (no notifications)
        - 1: Normal (only if mentioned)
        - 2: Tracking (notify on replies to your posts)
        - 3: Watching (notify on all new posts)

Must call login() first.

Returns a SubscriptionResult with:
- success: Whether subscription succeeded
- notification_level: The new notification level

Use to:
- Watch topics for all updates (level=3)
- Mute noisy topics (level=0)
- Track topics you've contributed to (level=2)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic_id`	Yes	The topic ID to subscribe to
`level`	No	Notification level: 0=muted, 1=normal, 2=tracking (default), 3=watching

Output Schema

TableJSON Schema

Name	Required	Description	Default
`success`	Yes	Whether subscription succeeded
`notification_level`	No	New notification level

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 authentication requirements ('REQUIRES AUTHENTICATION'), the mutation nature of setting notification levels, and the return structure. However, it doesn't mention potential side effects like rate limits or error conditions.

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 with clear sections (purpose, args, prerequisites, returns, use cases). Every sentence adds value without redundancy. It's front-loaded with the core purpose and efficiently organized for quick comprehension.

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 (2 parameters, mutation operation) and the presence of an output schema (returns SubscriptionResult), the description provides complete context. It covers authentication needs, parameter semantics, return values, and practical use cases, leaving no significant gaps for the agent.

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 semantic meaning of each level value with clear examples (0=muted, 1=normal, etc.), which goes beyond the schema's basic enumeration. It also clarifies that topic_id is required and level has a default of 2.

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 starts with a specific verb ('Set') and resource ('notification level for a topic'), clearly stating what the tool does. It distinguishes from siblings like get_topic_info or get_topic_posts by focusing on subscription management rather than information retrieval.

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 explicitly states 'Must call login() first' for authentication prerequisites and provides clear use cases with specific level values (e.g., 'Watch topics for all updates (level=3)', 'Mute noisy topics (level=0)'). It distinguishes when to use this tool versus alternatives by focusing on subscription actions.

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