Skip to main content
Glama
Sign In
preset-mcp

preset-mcp

by Evan-Kim2028
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_dashboard

Deletes a specified dashboard after exporting a full backup. Use dry_run to test without deletion.

Instructions

Delete a dashboard after exporting a full backup.

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

Input Schema

NameRequiredDescriptionDefault
dashboard_idYes
dry_runNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It identifies the action as destructive but does not elaborate on cascading effects, reversibility, or permission requirements, which are critical for a delete operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, making it concise, but it sacrifices completeness. It is front-loaded with the action but omits important details, striking a balance between brevity and clarity.

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?

Despite an output schema existing, the description does not explain return values or error scenarios. For a destructive tool, this lack of completeness hinders an agent's ability to handle responses 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 description provides no information about the two parameters (dashboard_id, dry_run). Given 0% schema coverage, the agent must infer meaning solely from parameter names, which is insufficient for confident use.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 resource ('a dashboard'), and adds a prerequisite ('after exporting a full backup'). This distinguishes it from other delete tools and informs the agent of a required precondition.

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 context by specifying the backup prerequisite, but it does not explicitly state when to use this tool vs alternatives (e.g., archival or disable actions) nor when not to use it.

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