contextium-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

get_notifications

Access your notification inbox to view activity notifications and broadcasts, with optional filters for unread items, pagination, and workspace selection.

Instructions

Get the notification inbox for the current user — both activity notifications and broadcasts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_notifications"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max notifications to return (default 20).
`offset`	No	Pagination offset (default 0).
`unreadOnly`	No	Only return unread notifications.
`workspaceId`	No	Workspace ID. Defaults to configured workspace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 10, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It implies a read operation but does not explicitly state that it is non-destructive, nor does it mention any limitations (e.g., it does not mark notifications as read). The description lacks behavioral details that would help avoid misunderstandings.

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 a single clear sentence with no unnecessary words, properly front-loaded with the action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list retrieval with no output schema, the description is sufficient to understand what the tool does. However, it could be improved by briefly mentioning what the response contains (e.g., list of notification objects with fields). Given the context signals (4 params, no nested objects), the description is mostly complete but leaves the return format unspecified.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema-provided parameter descriptions. It does not explain parameter relationships or defaults beyond what is already stated.

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?

Clearly states the tool retrieves the notification inbox for the current user, specifying it includes both activity notifications and broadcasts. This verb+resource combination is specific and distinguishes it from siblings like get_unread_count or mark_notification_read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like get_unread_count, mark_notification_read, or dismiss_broadcast. The description states what it does but provides no context for selection.

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

Deploy Server