Skip to main content
Glama

NEM Explorer (ScadaMiner)

get_dashboard

Read-onlyIdempotent

Read one saved dashboard's current spec — its queries and panels — by name or title. ALWAYS call this before editing one. save_dashboard replaces the whole spec rather than patching it, so an edit built from memory silently drops every panel you did not happen to remember. The response comes back in exactly the shape save_dashboard takes, so an edit is: get it, change the part the user asked about, send it all back. Its last_save is what the save behind this revision found — each query's cost, and any cost_warnings, data_warnings or empty_queries.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWhich dashboard, as its name (`sa-wind-vs-price`) or its title ("SA wind vs price"). Both resolve to the same one, so pass whichever the user said.
question_idNoOptional UUID returned by an earlier `start_question` call. When provided, this tool call is attributed to that question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/non-destructive already cover safety) by disclosing that the response is shape-compatible with save_dashboard's input and that it carries last_save data including per-query cost, cost_warnings, data_warnings, and empty_queries. It also explains the consequence of skipping the call (silently dropped panels), which is real behavioral context an agent cannot get from structured fields.

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

Conciseness4/5

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

The requirement and rationale are front-loaded and every sentence carries information. The final sentence about last_save is dense and slightly convoluted ("what the save behind this revision found"), costing a little readability, but there is no filler.

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?

There is no output schema, so the description carries the return-value burden and does so — it describes the response shape, the round-trip with save_dashboard, and the diagnostic fields in last_save. Nothing an agent needs to call this correctly and use the result is missing.

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 coverage is 100% and the schema already documents that name accepts a name or a title and what question_id is for. The description restates the name-or-title resolution but says nothing about question_id or its attribution behavior, so it adds little beyond the schema.

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?

Names a specific verb and resource ("Read one saved dashboard's current spec — its queries and panels") plus the lookup key (name or title). It is immediately distinguishable from save_dashboard, list_dashboards, and delete_dashboard without opening any schema.

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?

Gives an explicit precondition ("ALWAYS call this before editing one") and names the alternative it pairs with, explaining why: save_dashboard replaces the whole spec rather than patching it. The stated workflow — get it, change the requested part, send it all back — leaves no ambiguity about when this tool is required.

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.