Skip to main content
Glama
suthio

Redash MCP Server

by suthio

list_alerts

Lists all alerts in your Redash instance, summarizing each alert's configuration and status.

Instructions

List all alerts in Redash

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'list_alerts' tool. Calls redashClient.getAlerts() and returns the result as JSON.
    async function listAlerts() {
      try {
        const result = await redashClient.getAlerts();
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        logger.error(`Error listing alerts: ${error}`);
        return {
          isError: true,
          content: [{ type: "text", text: `Error listing alerts: ${error instanceof Error ? error.message : String(error)}` }]
        };
      }
    }
  • src/index.ts:1959-1967 (registration)
    Registration of the 'list_alerts' tool in ListToolsRequestSchema, defining its name, description, and input schema (empty object).
    // Alert tools
    {
      name: "list_alerts",
      description: "List all alerts in Redash",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • src/index.ts:2446-2449 (registration)
    Dispatch/case handler for 'list_alerts' in CallToolRequestSchema switch statement, calling the listAlerts() function.
    // Alert tools
    case "list_alerts":
      logger.debug(`Handling list_alerts`);
      return await listAlerts();
  • The getAlerts() method on RedashClient that makes the actual HTTP GET /api/alerts call to the Redash API.
    // Get all alerts
    async getAlerts(): Promise<RedashAlert[]> {
      try {
        const response = await this.client.get('/api/alerts');
        return response.data;
      } catch (error) {
        logger.error(`Error fetching alerts: ${error}`);
        throw new Error(`Failed to fetch alerts: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
Behavior2/5

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

No annotations provided, and the description fails to mention any behavioral aspects like pagination, rate limits, or authentication requirements; beyond being a read operation, it adds nothing.

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?

Single sentence, front-loaded, no extraneous words; appropriately concise for a simple list-all tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no parameters, the description does not clarify the return format or scope (e.g., all alerts across all users or only current user's alerts); with no output schema, this leaves ambiguity.

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?

No parameters exist, so the description does not need to explain them; baseline 4 applies as schema coverage is trivially 100%.

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 the action 'List' and the resource 'alerts in Redash', distinguishing it from sibling tools like get_alert (single) and create_alert.

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?

No guidance on when to use this tool vs alternatives such as get_alert or get_alert_subscriptions; no context on prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suthio/redash-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server