Skip to main content
Glama

rr_list_alerts

Read-onlyIdempotent

Retrieve active inventory alerts such as stockout warnings, sync failures, and anomalies, with filters for SKU, store, severity, status, and alert type.

Instructions

Get active alerts (stockout warnings, sync failures, anomalies).

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

Input Schema

NameRequiredDescriptionDefault
skuNoOnly alerts for this product, under any SKU it has had.
limitNoRows per page (default 50, max 500).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.
offsetNoDeprecated: rows to skip. Use cursor; it stays correct while rows change.
statusNoFilter: active, acknowledged
severityNoOnly alerts of this severity.
store_idNoOnly alerts for this store.
alert_typeNoAlert type filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

C2.9/5.0
Behavior2/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 the enumeration of alert categories and says nothing about paging behavior (cursor vs. deprecated offset), result volume, or freshness of alerts, so its incremental value beyond the annotations is thin.

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?

One short sentence with the resource front-loaded and no filler; the parenthetical examples are compact and informative. The minor cost is that "active" is a looser framing than the schema's status enum, but the wording itself is efficient.

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

Completeness3/5

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

With 8 optional parameters, pagination via cursor, and no output schema, an agent can call this correctly from the schema alone, and the annotations cover safety. However, the description leaves out what an alert record contains and how the status/severity/alert_type filters relate, so it is adequate rather than complete for a tool of this breadth.

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%, so every parameter (sku, limit, cursor, offset, status, severity, store_id, alert_type) is already documented in the schema, and the description adds no syntax, defaults, or filter-combination semantics. Baseline 3 is appropriate where the schema carries the parameter burden.

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?

"Get active alerts" gives a specific verb and resource and parenthesizes the alert taxonomy (stockout warnings, sync failures, anomalies), which helps distinguish it from neighboring list tools such as rr_list_stockout_risks. It stops short of explicitly contrasting itself with any sibling, so a 5 isn't warranted.

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 when-to-use or when-not-to-use guidance and no named alternative (e.g., rr_list_stockout_risks for forward-looking risk vs. already-fired alerts). The word "active" implies a scope but is not reconciled with the status filter that also allows "acknowledged", leaving the agent to infer the intended call context.

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