Skip to main content
Glama

ADS Beast

list_alerts

Read-only

Return the performance and delivery alerts raised by the ADS Beast monitoring agents, with their severity, the client or campaign they concern and whether they have been read or resolved.

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_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, newest first. Clamped into 1..5000 before the request. A page is also cut to fit the response size limit; when the reply has has_more = true, call again with offset = next_offset.
offsetNoAlerts to skip; use next_offset from the previous page.
is_readNoFalse returns only alerts nobody has read yet.
severityNoRestrict to one severity.
client_idNoRestrict to one client.
alert_typeNoRestrict to one kind of alert.
campaign_idNoRestrict to one campaign.
is_resolvedNoFalse returns only alerts that are still open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds genuinely new context: the alerts originate from ADS Beast monitoring agents and each record carries severity, an owning client/campaign, and read/resolved state. It still says nothing about cross-client scope or freshness of the alert stream, which would matter for an openWorld read.

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 front-loaded sentence with no repetition or boilerplate, and the returned-field list is packed into the same sentence rather than a separate section. Slight trimming possible around the product-name phrasing, but no sentence is wasted.

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?

With eight optional params, 100% schema coverage, and no output schema, the description usefully compensates by enumerating the alert record fields an agent will see. What is missing is any statement of default scope (all clients? all statuses?) and its relationship to alerts_unread_count, which leaves a small but real gap for a paging, filterable list tool.

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 100% and every one of the eight parameters is already documented in-schema, including pagination mechanics and the severity enum. The description merely echoes the filterable concepts (severity, client/campaign, read/resolved) without adding format or interaction detail beyond the schema. Baseline 3 is appropriate when the schema carries this much weight.

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?

States a specific verb and resource: 'Return the performance and delivery alerts raised by the ADS Beast monitoring agents.' An agent knows exactly what it gets back and what fields each alert carries. It stops short of differentiating from the sibling alerts_unread_count, which the description never mentions.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The sibling alerts_unread_count is an obvious near-neighbor this tool overlaps with (it exposes is_read filtering), yet the description gives no routing rule between them. Usage is only inferable from the tool name and parameter list.

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.