Skip to main content
Glama
Sign In
Redash MCP Server

Redash MCP Server

by suthio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_my_queries

Retrieve a list of queries created by your account. Use pagination to control output.

Instructions

Get queries created by the current user

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_my_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (starts at 1)
pageSizeNoNumber of results per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • addedInput schema / properties / page / default
      Added value: +1
    • addedInput schema / properties / pageSize / default
      Added value: +25
  2. First observedv0.0.13

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It correctly indicates the filtering by current user but does not disclose pagination behavior, sorting, or authentication requirements. Adequate for a simple read operation.

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, no extraneous words. Efficiently communicates the core functionality.

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 list tool with two parameters fully described in schema, the description is adequate. Lacks details about return format or sorting, but not critical given tool simplicity.

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?

Input schema covers both parameters (page, pageSize) with descriptions, so schema coverage is 100%. Description does not add additional meaning beyond what schema already provides.

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 (get), resource (queries), and scope (created by current user). It distinguishes from sibling tools like list_queries, get_recent_queries, and get_favorite_queries.

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 when-to-use or when-not-to-use guidance. Usage is implied: to retrieve only the current user's queries. Does not mention alternatives or exclusion of other tools like list_queries.

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