Skip to main content
Glama
Sign In
redash-mcp

redash-mcp

by oceandepthz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

execute_query

Execute saved Redash queries and return row data. Set max_age=0 to bypass cache and get fresh results.

Instructions

保存済みクエリを実行し行データを返す。max_age=0でキャッシュ回避。

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": {
      "query_id": "<query_id>"
    },
    "name": "execute_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_ageNo
query_idYes
parametersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Without annotations, the description partially covers behavior: it returns row data and describes cache avoidance. However, it does not disclose potential side effects (e.g., if queries modify data), authentication needs, or error handling.

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?

The description is very concise, consisting of a single sentence that conveys the core action and a key parameter usage. No unnecessary words, but could be expanded slightly for clarity.

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?

Given the lack of output schema and three parameters, the description is incomplete. It mentions returning row data but no format, and only addresses max_age. Missing details on query_id, parameters usage, error conditions, and permissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description only adds meaning for the max_age parameter (cache avoidance). The required query_id and optional parameters are not explained, leaving the agent to infer from names alone.

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 tool executes a saved query and returns row data, with explicit mention of cache avoidance via max_age=0. This distinguishes it from sibling tools which focus on listing or retrieving metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives is provided. The cache avoidance hint offers some context, but there is no mention of prerequisites or when not to use it.

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