mcp-banshee

dispatch_alert

Notify a household by sending mythical couriers selected by severity, with stack count to summon multiple creatures for louder alerts.

Instructions

Notify the household by dispatching a mythical creature. Severity picks the courier; stack summons more of them.

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": {
      "message": "<message>"
    },
    "name": "dispatch_alert"
  }
}

Input Schema

Name	Required	Description
`stack`	No	How many of the same creature to dispatch (default 1).
`message`	Yes	What the household must be told.
`severity`	No	info \| notice \| warning \| urgent \| critical (default urgent)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It implies a notification-style, non-destructive action but never states side effects, delivery timing, permissions, or what happens on failure; the whimsical 'mythical creature' framing obscures rather than clarifies actual behavior.

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 short sentences with no filler; the core action leads and the parameter behavior follows immediately. Every sentence earns its place.

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?

For a simple three-parameter notification tool with full schema coverage and no output schema, the description covers purpose and parameter effects adequately. It omits any relationship to list_couriers and gives no sense of the outcome or confirmation returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description genuinely adds meaning: 'Severity picks the courier' explains that the enum selects the delivery mechanism, and 'stack summons more of them' clarifies that the integer is a multiplicity rather than an ID or index.

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 concrete action (notify the household) and the mechanism (dispatching a creature), so the agent knows this sends an alert rather than listing one. It does not, however, distinguish itself from the sibling list_couriers or clarify the relationship between them.

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 dispatch an alert versus other options, no prerequisites, and the sibling list_couriers is never referenced. The severity/stack behavior explains mechanics but not when this tool should be chosen.

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

Deploy Server