Skip to main content
Glama

TesterSwap

List notifications

list_notifications
Read-onlyIdempotent

Read your recent notifications, optionally unread only.

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
pageNo
unread_onlyNo

Output Schema

NameRequiredDescriptionDefault
totalYes
notificationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that results are 'recent', without defining the recency window, result volume, ordering, or pagination behavior — leaving behavior largely to the annotations and output schema.

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?

A single short sentence with the resource up front and the filter qualifier trailing correctly; no redundant restatement of the title. Its brevity is efficient, though it borders on under-specification rather than being padded.

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?

This is a simple two-parameter read tool with an output schema, so the description needn't explain return values. The remaining gap is the undefined 'recent' window and pagination semantics on the page parameter, which is minor given the tool's low complexity.

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 0%, so the description must carry parameter meaning. It does clarify unread_only ('optionally unread only'), but says nothing about the page parameter — no ordering assumption, page size, or what happens past the last page. One of two parameters is effectively covered, so a mid score with a clear gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Read your recent notifications') and mentions the optional unread filter, which distinguishes it from the sibling mark_notifications_read (mutation) without needing the schema. It stops short of explicitly stating the contrast with that sibling, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

The phrase 'optionally unread only' implies the main usage variant (filtering to unread), but there is no explicit when-to-use guidance, no statement of when to pick this over the related read/mark tools, and no mention of prerequisites or paging back through older notifications.

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.