Skip to main content
Glama
Sign In
aeza-mcp

aeza-mcp

by rdydygin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

notifications_get_list

Read-onlyIdempotent

Retrieve a paginated list of user notifications from Aeza, with sorting, filtering, and limit/offset controls to review account alerts and updates.

Instructions

Get list of user notifications GET /notifications

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
filterNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond restating the endpoint path – no pagination behavior, ordering defaults, or whether marking/read state is included in results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short lines, front-loaded and free of filler, but the brevity comes at the cost of under-specification rather than efficiency.

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

Completeness2/5

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

For a list endpoint with four undocumented query parameters and no output schema, the definition should at minimum explain filter/sort semantics and the default limit of 50. The annotations cover mutability, but the practical calling contract is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description mentions none of the four parameters (sort, limit, filter, offset). The agent cannot learn filter syntax, sort keys, or maximum page size from either source, which is the exact gap the description should fill.

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?

The description names a specific verb and resource ("Get list of user notifications"), so an agent knows exactly what it returns. It does not distinguish this from sibling notifications_get_one or the mark-as-read tools, but the core purpose is unambiguous.

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?

There is no guidance on when to use this versus notifications_get_one when the notification ID is known, nor any note on when the mark-as-read siblings should follow. The agent must infer the workflow entirely.

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

Deploy Server

Other Tools