Skip to main content
Glama
Sign In
preset-mcp

preset-mcp

by Evan-Kim2028
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_saved_query

Delete a saved query by its ID. Use dry_run to preview the action before executing.

Instructions

Delete a saved query.

Args: query_id: The saved query ID to delete. dry_run: If True, preview the action without executing.

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": "delete_saved_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
query_idYes
dry_runNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

A4.1/5.0
Behavior3/5

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

Without annotations, the description takes full burden. It discloses the destructive action and preview via dry_run, but omits details on permanence, required permissions, or side effects.

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 concise: one sentence for purpose, then structured parameter descriptions under 'Args:'. No redundant words.

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?

The description covers action and parameters adequately for a simple tool with an output schema. It could mention if deletion is permanent or requires confirmation, but overall it is fairly complete.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by explaining both parameters: 'query_id: The saved query ID to delete.' and 'dry_run: If True, preview the action without executing.' This adds essential meaning.

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 explicitly states 'Delete a saved query,' using a specific verb and resource. This clearly distinguishes it from sibling tools like create_saved_query, update_saved_query, and get_saved_query.

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?

The description implies usage for deletion but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions.

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