Skip to main content
Glama
Sign In
Redash MCP Server

Redash MCP Server

by suthio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

archive_query

Soft-delete a Redash query by its ID, moving it to the archive without permanent removal.

Instructions

Archive (soft-delete) a query in Redash

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": {
      "queryId": "<queryId>"
    },
    "name": "archive_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryIdYesID of the query to archive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.13

TDQS

A3.5/5.0
Behavior3/5

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

The term 'soft-delete' discloses that the operation is reversible rather than a permanent deletion, adding context beyond the bare action. However, it does not explain how soft-delete manifests in Redash (e.g., visibility, restoration), permission requirements, or effects on dependent objects.

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, front-loaded sentence that communicates the essential action efficiently with no wasted words.

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?

The tool is simple with one parameter, making the description adequate. However, it omits any mention of return values or error behavior, and since no output schema exists, a brief note on success/failure would improve completeness.

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?

The input schema fully describes queryId, and the description adds no additional parameter semantics. Baseline of 3 applies because schema coverage is 100%.

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 uses the specific verb 'archive' with the resource 'query', and clarifies it's a soft-delete operation. This clearly distinguishes it from sibling tools like update_query, get_query, and list_queries.

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 guidance is given about when to use this tool versus alternatives. The description doesn't mention prerequisites, the consequences of archiving, or when a soft-delete is preferred over other operations.

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