Redash MCP Server

get_recent_queries

Retrieve a paginated list of recently accessed queries from Redash. Specify page and page size to control results.

Instructions

Get recently accessed queries

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_queries"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number (starts at 1)
`pageSize`	No	Number of results per page

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.1Jul 6, 2026
- addedInput schema / properties / page / default
```
Added value: +1
```
- addedInput schema / properties / pageSize / default
```
Added value: +25
```
First observedv0.0.13May 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and resource, omitting key behavioral details such as auth requirements, read-only nature, pagination behavior (despite schema parameters), or what data is returned (e.g., query metadata vs. content).

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 a single, clear sentence with no wasted words. While minimal, it efficiently communicates the core purpose. Slightly more context (e.g., scope of 'recently accessed') could be added without harming conciseness.

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 no output schema and no annotations, the description is incomplete. It fails to explain what 'recently accessed' means (e.g., time window, user-specific vs. collaborative), how pagination works, or what the response contains. A more complete description is warranted for a tool with these parameters and siblings.

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

Parameters3/5

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

Schema description coverage is 100% for the two parameters (page and pageSize). The description adds no additional meaning beyond what the schema already provides, meeting the baseline for this dimension.

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 tool retrieves recently accessed queries, distinguishing it from siblings like list_queries (all queries) and get_my_queries (user's own queries). However, it does not specify what constitutes 'recently accessed' (timeframe or user scope), leaving some ambiguity.

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. The description does not indicate when to use this tool over alternatives (e.g., get_my_queries or list_queries) nor any prerequisites or conditions for use.

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

Deploy Server