Skip to main content
Glama

list_notifications

List the user's Bilg notifications across all their projects: what other people — and other people's agents — did that concerns the user (question resolved/reopened/asked, comments on their items, handoffs received/replied/resolved, assignments, epic stage changes). The user's own actions and their own agents' actions never appear. Use it for "what did others do since X": pass since (ISO 8601). Read-only: it never marks anything read or delivered, so the same call returns the same result. Newest first; page with cursor.

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": "list_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-50, default 20
sinceNoYYYY-MM-DD or ISO 8601 timestamp with Z or ±HH:MM offset, e.g. 2026-11-13T09:00:00Z; returns notifications created after it
cursorNonextCursor from a previous call
unreadOnlyNoOnly unread notifications

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it declares read-only behavior, non-mutation of read state ("never marks anything read or delivered"), and idempotence ("the same call returns the same result"). It omits auth/permission requirements and how far back notifications are retained, keeping it below a 5.

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?

Purpose is front-loaded in the first clause, then scope, then behavior and paging — a logical progression with no filler. The event-type parenthetical is dense but each item helps an agent decide relevance, so the length is largely earned.

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?

Covers the essentials for a read-only list tool: scope, exclusions, ordering, pagination, and non-mutation guarantees, which matters since there is no output schema. The one gap is that the shape of returned notification items (fields available per entry) is never hinted at.

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 coverage is 100%, so the baseline is 3, but the description adds ordering and paging semantics the schema lacks: results are newest first and paging is done with `cursor`, and `since` is framed as the "what did others do since X" filter. It does not clarify unreadOnly interactions or limit defaults beyond the schema.

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?

Specific verb+resource with explicit scope: "List the user's Bilg notifications across all their projects," followed by an enumeration of the covered events (questions resolved/reopened/asked, comments, handoffs, assignments, epic stage changes). This clearly separates it from per-resource siblings like list_handoffs or list_open_questions by being the aggregated feed of other people's actions.

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

Usage Guidelines4/5

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

Gives an explicit usage pattern — "Use it for 'what did others do since X': pass `since`" — plus a strong exclusion rule: the user's own and their own agents' actions never appear. It stops short of naming a concrete alternative tool for viewing the user's own activity, so it is clear context without full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources