Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

Delete Saved Query

delete-saved-query
DestructiveIdempotent

Delete a saved query you own by its id. Requires a user session or OAuth; API keys are not supported. Deletes only the saved definition and does not execute SQL or delete underlying data.

Instructions

Delete a saved query you own by its id. Requires a user session or OAuth; API keys are not supported. Deletes only the saved definition and does not execute SQL or delete underlying data. Returns { id, deleted: true } after successful deletion.

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": {
      "id": "<id>"
    },
    "name": "delete-saved-query"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the saved query to delete.
clusterNoRawTree cluster to use for this operation.
organizationNoRawTree organization containing the target cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.2

TDQS

A4.2/5.0
Behavior4/5

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

With destructiveHint=true and idempotentHint=true already declared, the description still adds real value: the exact destruction boundary (definition only, no data), the authentication constraint (API keys unsupported), and the success return shape. What it omits is the behavior on a missing or non-owned id, which matters given the idempotent hint.

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?

Four short sentences, each carrying distinct information: action, auth requirement, blast radius, and return value. The action and scope are front-loaded with no filler.

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?

Covers auth, destruction scope, and the return value even though no output schema exists. The one gap is failure semantics for a nonexistent or unowned query id, which an agent needs given the idempotency declaration.

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%, so all three parameters are already documented, establishing a baseline of 3. The description adds only the ownership qualifier on id and says nothing about the cluster/organization parameters beyond what the schema states.

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?

States a specific verb and resource ('Delete a saved query') plus an ownership scope ('you own') and the identifier basis ('by its id'). This clearly separates it from sibling deletions such as delete-table, delete-database, delete-workflow, and delete-api-key.

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

Usage Guidelines4/5

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

The description sets the boundary 'Deletes only the saved definition and does not execute SQL or delete underlying data,' which effectively tells the agent when this is the wrong tool (data/SQL deletion). It also states the auth context (session/OAuth, not API keys). It does not point at list-saved-queries as the way to obtain an id, so it stops short of full alternative routing.

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