Skip to main content
Glama

NEM Explorer (ScadaMiner)

list_dashboards

Read-onlyIdempotent

List the saved dashboards belonging to the signed-in user: name, title, panel count and URL. Call this FIRST whenever the user refers to a dashboard they already have ("update my price dashboard", "what dashboards do I have") — the names here are what get_dashboard, save_dashboard and delete_dashboard take. Private to the caller; there is no way to see anyone else's.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dashboards"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the result set is private to the caller with no cross-user visibility, and the listed fields are what downstream dashboard tools accept. It doesn't discuss empty states (no dashboards saved) or ordering, which keeps it short of a 5.

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?

Three sentences, front-loaded with purpose, then the call-first rule, then the privacy constraint. Every clause carries information the agent needs: what it returns, when to call it, and what it cannot see. 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?

With no output schema, the description compensates by naming the returned fields, and it covers the privacy boundary and the sequencing requirement. For a read-only single-parameter list tool, an agent has everything it needs to select and invoke it correctly.

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?

There is one optional parameter (question_id) with 100% schema description coverage, so the schema already explains it fully. The description adds no parameter-level meaning at all, which is the expected baseline when schema coverage is high rather than a defect.

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 opens with a specific verb and resource ("List the saved dashboards belonging to the signed-in user") and then enumerates the returned fields (name, title, panel count, URL). That scope statement — saved dashboards owned by the caller — cleanly separates it from list_live_queries, list_results, and list_tables without needing their schemas.

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?

It states an explicit trigger ("Call this FIRST whenever the user refers to a dashboard they already have") and backs it with two concrete user utterances. It also explains why ordering matters and names three siblings (get_dashboard, save_dashboard, delete_dashboard) as the consumers of the returned names, so the agent knows this is a discovery step.

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.