Skip to main content
Glama
Sign In
redash-mcp

redash-mcp

by seob717
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_alert

Destructive

Create an alert that watches a saved query and triggers when a specified column meets a condition (greater than, less than, or equals) a threshold.

Instructions

Create an alert that watches a saved query and fires when a chosen result column crosses a threshold (e.g., daily_signups less than 10). Behavior: creates the alert and returns its id and name. Usage: get the query_id from list_queries and confirm the exact column name with get_query / get_query_result first. The alert evaluates the query's latest result on Redash's schedule.

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": {
      "name": "<name>",
      "query_id": "<query_id>",
      "column": "<column>",
      "op": "<op>",
      "value": "<value>"
    },
    "name": "create_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesComparison operator between the column value and the threshold
nameYesDisplay name for the alert
rearmNoSeconds to wait before the alert can fire again; 0 means fire only once until manually reset (default 0)
valueYesThreshold value that triggers the alert when the comparison is true
columnYesName of the result column to compare against the threshold
query_idYesID of the saved query whose results are monitored (from list_queries)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.2.0
    • changedInput schema / properties / column / description
      Previous value: -"Column name to monitor"New value: +"Name of the result column to compare against the threshold"
    • changedInput schema / properties / name / description
      Previous value: -"Alert name"New value: +"Display name for the alert"
    • changedInput schema / properties / op / description
      Previous value: -"Comparison operator"New value: +"Comparison operator between the column value and the threshold"
    • changedInput schema / properties / query_id / description
      Previous value: -"Query ID to monitor"New value: +"ID of the saved query whose results are monitored (from list_queries)"
    • changedInput schema / properties / rearm / description
      Previous value: -"Rearm interval in seconds (0 = fire once)"New value: +"Seconds to wait before the alert can fire again; 0 means fire only once until manually reset (default 0)"
    • changedInput schema / properties / value / description
      Previous value: -"Threshold value"New value: +"Threshold value that triggers the alert when the comparison is true"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, consistent with creation. Description adds that it returns id and name, and explains evaluation schedule. No contradictions.

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 plus a usage note: efficient, front-loaded, no unnecessary words. Every sentence adds value.

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 creation tool with 6 params and no output schema, description provides purpose, behavior, return info, and usage tips. Adequately complete for the tool's complexity.

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 covers all parameters with descriptions. The description adds usage context like 'from list_queries' and 'confirm exact column name', enhancing understanding beyond raw schema.

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?

The description clearly states it creates an alert that monitors a saved query and fires on a threshold, with an explicit example. Among sibling tools, no other creates alerts, so it is well-distinguished.

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?

Explicitly advises to obtain query_id from list_queries and verify column name via get_query/get_query_result. Does not specify when not to use, but context is clear for a creation tool.

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

Deploy Server

Other Tools