Skip to main content
Glama

WhatsDownNow

Read an alert stack

get_alert_stack
Read-onlyIdempotent

Read a stack you created: its services and their current status, alert rules, delivery channels (including whether an email is confirmed), firing alerts and recent deliveries. Needs the stack id and its management token.

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": {
      "stack_id": "<stack_id>",
      "token": "<token>"
    },
    "name": "get_alert_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesManagement token (wdn_...) returned once by create_alert_stack
stack_idYesStack id (stk_...) returned by create_alert_stack

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that: it requires the management token (an auth requirement) and discloses the rich returned inventory, including the email-confirmation flag. It does not mention pagination or limits on the 'recent deliveries' list.

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and the returned contents, then the credential prerequisite. The enumerated content list is dense but every item is informative, and there is no filler.

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 no output schema, the description carries the burden of describing return values, and it does so thoroughly across six categories of data. The only gap is operational detail such as how many 'recent deliveries' are returned or behaviour on an invalid or expired token.

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 both parameters are already documented in the schema, including the wdn_ and stk_ prefixes and the origin from create_alert_stack. The sentence 'Needs the stack id and its management token' only restates what the schema says, adding no format or constraint detail.

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?

A specific verb ('Read') plus resource ('stack') followed by an explicit inventory of what comes back: services and status, alert rules, delivery channels, firing alerts, recent deliveries. That is much more than a restatement of the name. It does not distinguish itself from lookalike siblings such as check_stack or get_status, so it stops short of 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?

Usage is only implied: 'a stack you created' plus the required credentials tells the agent this is the detail/inspection call, and the credential requirement is a real precondition. There is no explicit when-to-use versus check_stack or get_status, and no statement about when not to call it.

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.