Skip to main content
Glama
cameronrye

AT Protocol MCP Server

get_notifications

Read-only

Fetch user notifications from AT Protocol (likes, reposts, follows, mentions, replies). Use countOnly to get unread badge count without loading full list.

Instructions

Retrieve notifications from AT Protocol (likes, reposts, follows, mentions, replies). Requires authentication (app password). Use countOnly: true to fetch only the unread badge count cheaply without loading the full list; use mark_notifications_seen to clear the unread state after processing. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax notifications per page (1–100, default 50).
cursorNoOpaque pagination cursor from the previous response cursor field; omit for the first page.
seenAtNoISO 8601 timestamp; only return notifications that occurred after this time. Optional filter.
countOnlyNoWhen true, return only the unread count and skip fetching the notification list (cheap badge-number path).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the request succeeded.
unreadCountYesNumber of unread notifications (always present).
notificationsNoNotification entries. Present only when countOnly is false/absent.
cursorNoOpaque cursor for the next page. Present only when countOnly is false/absent.
hasMoreNoTrue when a next page is available. Present only when countOnly is false/absent.
seenAtNoThe timestamp up to which notifications have been seen. Present only when countOnly is false/absent.
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description adds value: requires auth, subject to rate limiting, countOnly skips full list. No contradiction with 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?

Three sentences, each purposeful, front-loaded with main action. No wasted words.

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?

For a read-only list tool with 4 parameters (all documented), annotations, and output schema, the description covers auth, rate limits, special logic (countOnly), and sibling reference. No gaps.

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 coverage is 100% with detailed parameter descriptions. The description reinforces countOnly but adds no new parameter semantics. Baseline 3 is appropriate.

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 clear verb ('Retrieve') and specific resource ('notifications from AT Protocol'), listing types (likes, reposts, etc.). It distinguishes itself from siblings like mark_notifications_seen by explicitly mentioning it.

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?

Provides explicit guidance: when to use countOnly for cheap badge count, when to use mark_notifications_seen to clear state. Also notes authentication and rate limiting, helping the agent decide context.

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/cameronrye/atproto-mcp'

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