Skip to main content
Glama

WhatsDownNow

Send a test alert

send_test_alert

Send a test alert to every active channel of a stack right now (confirmed emails, webhooks, browser push) so the user can see what alerts look like. 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": "send_test_alert"
  }
}

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the fan-out to every active channel, the concrete channel types (confirmed emails, webhooks, browser push), and the management-token requirement. It does not warn that repeated calls produce duplicate deliveries despite idempotentHint=false, which keeps it at 4.

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 what happens and to whom, followed by the prerequisite. Every clause (channel list, immediacy, token need) adds information; nothing is redundant.

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?

For a two-parameter action tool with full schema coverage, annotations, and no output schema, the description covers purpose, delivery scope, and auth requirements. Minor gaps remain around whether test alerts are visually marked as tests and any rate/latency expectations.

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%, including the wdn_ token format and stk_ id pattern, so the schema carries parameter meaning. The description only restates 'Needs the stack id and its management token' without adding format, sourcing, or scoping detail. Baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ('send a test alert') plus scope ('to every active channel of a stack right now') and enumerates the target channels. No sibling tool in the list does this, so it is distinguishable without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context via 'so the user can see what alerts look like', making the preview/verification intent explicit. It stops short of naming when-not to use it (e.g. not for real incidents) or pointing to an alternative such as check_stack, so it earns a 4 rather than a 5.

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.