Skip to main content
Glama

NEM Explorer (ScadaMiner)

delete_dashboard

Idempotent

Delete one of the user's saved dashboards, by name or title. Only call this when they have explicitly asked for the dashboard itself to go, and quote their words in user_request — "this panel is wrong" is a save_dashboard edit, not a deletion. If you are not certain which one they meant, call list_dashboards and ask. The row is retained internally so support can restore a mistake, but it disappears from the user's page immediately.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWhich dashboard, as its name or title.
question_idNoOptional UUID returned by an earlier `start_question` call. When provided, this tool call is attributed to that question.
user_requestYesREQUIRED. The user's own words asking for this dashboard to be deleted, quoted verbatim — e.g. "delete my price dashboard", "get rid of the SA wind one". Deleting is not something to infer from "that one's not useful any more". Quoting the request is how you check they asked for the dashboard to go, rather than for a panel to change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructiveHint=false and idempotentHint=true, which could read as contradictory for a delete tool; the description resolves this by disclosing soft-delete semantics ("The row is retained internally so support can restore a mistake") and the immediate user-visible effect ("it disappears from the user's page immediately"). That is real behavioral context the annotations cannot convey on their own.

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 in a deliberate order: action, gating condition, fallback, then post-call behavior. The quoted-example contrast is dense with signal rather than padding, and nothing is repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter destructive-ish tool with no output schema, the description covers the precondition, the identifier form, the disambiguation route, and the resulting state change. An agent has everything needed to call it correctly or decline to.

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 the schema already documents `name`, `question_id`, and the verbatim-quoting requirement on `user_request`. The description reinforces the verbatim-quote idea but adds no new syntax, format, or constraints beyond what the schema states, so this sits at the baseline.

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?

Specific verb plus resource ("Delete one of the user's saved dashboards") with the identifier form stated ("by name or title"). It explicitly separates itself from the nearest sibling by ruling out edits: "'this panel is wrong' is a `save_dashboard` edit, not a deletion."

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

Usage Guidelines5/5

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

States a precondition ("Only call this when they have explicitly asked for the dashboard itself to go"), a named counter-case routed elsewhere (panel fix -> save_dashboard), and a disambiguation path ("If you are not certain which one they meant, call `list_dashboards` and ask"). All three of when/when-not/alternative are present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.