Skip to main content
Glama
suthio

Redash MCP Server

by suthio

list_destinations

Retrieve a list of all alert notification destinations, such as email and Slack, to view or manage where alerts are sent.

Instructions

List all alert notification destinations (email, Slack, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_destinations' tool. Calls redashClient.getDestinations() and returns the result.
    // Tool: list_destinations
    async function listDestinations() {
      try {
        const result = await redashClient.getDestinations();
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        logger.error(`Error listing destinations: ${error}`);
        return {
          isError: true,
          content: [{ type: "text", text: `Error listing destinations: ${error instanceof Error ? error.message : String(error)}` }]
        };
      }
    }
  • src/index.ts:2280-2288 (registration)
    Tool registration entry for 'list_destinations' in the ListToolsRequestSchema handler, defining its name, description, and empty inputSchema.
    // Destination tools
    {
      name: "list_destinations",
      description: "List all alert notification destinations (email, Slack, etc.)",
      inputSchema: {
        type: "object",
        properties: {}
      }
    }
  • src/index.ts:2554-2557 (registration)
    The case in the CallToolRequestSchema switch statement that routes 'list_destinations' calls to the listDestinations() handler.
    // Destination tools
    case "list_destinations":
      logger.debug(`Handling list_destinations`);
      return await listDestinations();
  • The RedashDestination interface definition used as the type for the destinations data.
    // Destination interface
    export interface RedashDestination {
      id: number;
      name: string;
      type: string;
      options: any;
    }
  • The redashClient.getDestinations() method that performs the actual API call to GET /api/destinations.
      // ----- Destination API Methods -----
    
      // Get all destinations
      async getDestinations(): Promise<RedashDestination[]> {
        try {
          const response = await this.client.get('/api/destinations');
          return response.data;
        } catch (error) {
          logger.error(`Error fetching destinations: ${error}`);
          throw new Error(`Failed to fetch destinations: ${error instanceof Error ? error.message : String(error)}`);
        }
      }
    }
Behavior2/5

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

No annotations are present, and the description only states the action without disclosing any behavioral traits such as authentication needs, rate limits, or side effects.

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?

The description is extremely concise with a single sentence that is front-loaded with the core action and examples, containing no unnecessary words.

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 simple zero-parameter list tool, the description is largely sufficient, though it lacks details about the output structure (e.g., fields returned), which is not covered by an output schema.

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?

With no parameters, the description adds meaning by specifying the resource type (alert notification destinations), which is not detailed in the empty input 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 lists all alert notification destinations with examples (email, Slack), making the purpose specific and distinct from sibling tools like list_alerts which list alerts themselves.

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 usage guidelines are provided; there is no mention of when to use this tool versus alternatives or any prerequisites.

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