USCardForum MCP Server

get_notifications

Fetch user notifications from USCardForum to check replies, mentions, likes, and topic updates with optional filters for unread items and time ranges.

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

Name	Required	Description
`since_id`	No	Only get notifications newer than this ID
`only_unread`	No	Only return unread notifications
`limit`	No	Maximum number to return

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 30, 2025

TDQS

A4.4/5.0

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.