Skip to main content
Glama
Sign In
tick-mcp

tick-mcp

by KpihX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_query_preset

Delete a saved query preset by name. Use this to remove unwanted presets from your query preset list.

Instructions

Delete a saved query preset.

[Category: Query & Search]  [Auth: none]
[Related: list_query_presets, save_query_preset, run_query_preset]

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only mentions 'Auth: none' but does not describe side effects, error handling, or any irreversible consequences of deletion. This is insufficient for a destructive 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?

The description is extremely concise with one sentence plus metadata. It is front-loaded and contains no wasted words.

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?

For a simple delete tool, the description lacks parameter explanation, return value, error conditions, and any usage context beyond the action. Without annotations or output schema, this is insufficient for an agent to invoke correctly.

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

Parameters1/5

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

The schema has one parameter 'name' with 0% description coverage, and the description does not mention it at all. No meaning is added beyond the schema, leaving the agent without guidance on what string to provide.

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 'Delete' and the resource 'saved query preset', making the purpose unambiguous. It is distinct from sibling tools like list_query_presets, save_query_preset, and run_query_preset.

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 lists related tools but provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or conditions. The context is clear but lacks exclusions or usage scenarios.

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