Skip to main content
Glama
jasonsmithj

Redash MCP Server

by jasonsmithj

list_data_sources

Retrieve all configured data sources available in Redash for query execution and data analysis.

Instructions

List all available data sources in Redash

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Full implementation of the list_data_sources tool handler, which takes no arguments, calls RedashClient.listDataSources(), stringifies the result as JSON, and handles errors.
    export const listDataSourcesTool: Tool = {
      name: 'list_data_sources',
      description: 'List all available data sources in Redash',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false,
      },
      handler: async (_args, client) => {
        try {
          const dataSources = await client.listDataSources();
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(dataSources, null, 2),
              } as TextContent,
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error listing data sources: ${error instanceof Error ? error.message : String(error)}`,
              } as TextContent,
            ],
            isError: true,
          };
        }
      },
    };
  • Input schema for list_data_sources tool: empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false,
    },
  • src/index.ts:59-59 (registration)
    Registration of listDataSourcesTool in the tools array used by MCP server handlers.
    const tools = [listDataSourcesTool, getDataSourceTool, executeQueryAndWaitTool, listQueriesTool];
  • src/index.ts:16-16 (registration)
    Import of listDataSourcesTool for registration.
    import { listDataSourcesTool, getDataSourceTool } from './tools/datasource.js';
  • Helper method on RedashClient used by the tool handler to fetch data sources via API.
    async listDataSources(): Promise<DataSource[]> {
      return this.request<DataSource[]>('/api/data_sources');
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List all available data sources') but doesn't describe behavioral traits such as whether this is a read-only operation, if it requires authentication, how results are returned (e.g., pagination, format), or any rate limits. This leaves significant gaps for an agent to understand the tool's 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?

The description is a single, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded with the core action and resource, making it highly efficient and easy to parse.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate. It states what the tool does, but without annotations or output schema, it lacks details on behavior and return values. For a list operation, more context on result format or constraints would be helpful, but it meets the basic threshold for such a simple tool.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is applied for tools with no parameters, as there's nothing to compensate for.

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?

The description clearly states the verb ('List') and resource ('all available data sources in Redash'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_data_source' (which likely retrieves a single data source) or 'list_queries' (which lists queries rather than data sources), missing full sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like needing a list versus a single data source (vs. 'get_data_source') or when to use this versus 'list_queries', nor does it specify any prerequisites or exclusions for usage.

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/jasonsmithj/redash-mcp'

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