Skip to main content
Glama

Test notification route

test_notification_route
Destructive

Queue a sample notification through a notification route's destination (the twin of ankra alerts routes test) to prove the route delivers - to the webhook destination, or for a push route to the caller's own registered devices. Delivery is asynchronous: check the channel. Requires alerts.write.

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": {
      "route_id": "<route_id>"
    },
    "name": "test_notification_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
route_idYesNotification route id (UUID) from list_notification_routes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false), the description adds real behavioral context: delivery is asynchronous and the result must be checked elsewhere, alerts.write permission is required, and for push routes the sample lands on the caller's own registered devices — a side effect an agent needs to know before invoking. It does not explain how the 'channel' result is observed, slighting the async claim.

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 dense sentence with the action front-loaded, followed by the purpose and the delivery-mode detail. The CLI-twin parenthetical and the phrase 'to prove the route delivers' are mildly redundant but earn their place as orientation. No filler sentences.

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?

There is no output schema, so the description carries the burden of explaining what happens after the call, and 'check the channel' is vague — it never says where or how the delivery result surfaces. For a simple one-parameter tool with annotations covering safety, the definition is otherwise adequate, but the async result path is a meaningful omission.

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 coverage is 100%; route_id is already documented in the schema as a UUID obtainable from list_notification_routes. The description adds no further meaning about the parameter beyond establishing that its destination determines delivery behavior. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 ('Queue a sample notification through a notification route's destination') and describes the goal ('to prove the route delivers'). It also maps itself to the CLI equivalent ('the twin of `ankra alerts routes test`') and distinguishes the two destination modes (webhook vs. push to caller's own devices), which separates it from list/get/update siblings.

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?

It gives a clear reason to call this tool: verifying that a route actually delivers, which implicitly distinguishes it from configuration siblings like update_notification_route or get_notification_route. It does not explicitly exclude or compare against preview_notification_routing, so the boundary with that sibling is left to inference.

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.