Gameball MCP Server

Overview Schema Source Related Servers Discussions Admin

listCustomerNotifications

Retrieve a customer's notifications with filters for language, read status, and pagination to display relevant messages.

Instructions

Get notification

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customerId": "<customerId>"
    },
    "name": "listCustomerNotifications"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Language in which notification
`limit`	No	Number of notifications to ret
`isRead`	No	Filter notifications based on
`customerId`	Yes
`startAfter`	No	Specifies the page will start

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

D1.9/5.0

Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits. It does not state that this is a read-only operation, what the return format is, or how pagination/filtering works. The description carries the full burden and fails completely.

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

Conciseness2/5

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

The description is extremely under-specified at just two words. This is not efficient conciseness but rather a lack of substance, providing no actionable information for an agent.

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

Completeness1/5

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

This tool has 5 parameters, no output schema, and no annotations. The description 'Get notification' gives no information about behavior, return values, pagination, or filter semantics, making it severely incomplete for a list operation.

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 80%, so the baseline is 3. The tool description itself adds no parameter meaning, but the schema does provide some descriptions (albeit truncated). The description does not actively confuse, so a baseline score is appropriate.

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

Purpose2/5

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

The description 'Get notification' is vague and under-specified; it does not clearly state that this tool lists notifications for a customer. It also fails to distinguish itself from sibling tools like getCustomerNotificationsCount or markNotificationsRead, which also relate to notifications.

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 tool versus alternatives, nor any mention of pagination, filtering, or prerequisites such as the customerId. The description provides no context for selecting this tool.

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

Deploy Server