Skip to main content
Glama

NEM Explorer (ScadaMiner)

share_dashboard

Idempotent

Make one of the user's saved dashboards PUBLIC at an unguessable URL — or revoke that link with revoke: true. Anyone with the link sees the dashboard's LIVE warehouse data with no sign-in, served from a shared server-side cache so viewers cannot run up query costs. Only call this when the user has explicitly asked to share or publish the dashboard, and quote their words in user_request — the tool refuses otherwise, exactly like share_artifact. Idempotent: sharing twice returns the same URL. Revoking kills the link permanently; sharing again afterwards mints a NEW URL. The returned page accepts ?marquee=1 (chrome-free, for wall displays), &refresh=<seconds> (auto-refresh, min 30), and &panel=<n> (single panel). A request to host it on a search-friendly or SEO link counts as asking to share; once an admin lists it for search it is also served at the readable /nem/<slug> (see the dashboard guide). For a one-off analysis write-up use share_artifact instead — this is for a live page someone returns to.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWhich dashboard, as its name or title.
revokeNoPass `true` to REVOKE the public link instead of creating one. The link dies immediately and permanently — sharing again later mints a NEW URL, so anyone holding the old one stays locked out.
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 made public (or private again), quoted verbatim — e.g. "share my price dashboard", "make it public", "host it on an SEO-friendly link", "kill the public link". Sharing puts live warehouse data behind a URL anyone can open with no sign-in. That is not something to infer — if you cannot point at words asking for it, ask the user first and tell them what public means here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only give a bare safety profile; the description adds substantial context: viewers hit live warehouse data with no sign-in, but through a shared server-side cache so they cannot run up query costs, sharing is idempotent and returns the same URL, revoking permanently kills the link and a later share mints a new one. It also documents the returned page's query parameters (`?marquee=1`, `&refresh`, `&panel`), which no structured field provides.

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?

Purpose and the unguessable-URL model are front-loaded before the safety gate and the alternative. Nearly every sentence carries new information, though the permanence/idempotency sentence partly restates what the `revoke` schema description already says, and the trailing query-parameter sentence is dense relative to its importance.

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?

No output schema exists, so the description compensates by describing what is returned (a URL, stable across repeated shares, with optional display parameters) and what happens on the destructive path. For a 4-parameter share/revoke tool with a refusal gate, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining the refusal semantics of `user_request` ('quote their words... the tool refuses otherwise') and the 'ask the user first and tell them what public means here' guidance. `revoke` and `question_id` are largely left to the schema, with only modest added nuance beyond the existing descriptions.

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?

Opens with a precise verb and resource: making one of the user's saved dashboards public at an unguessable URL, or revoking that link via `revoke: true`. It explicitly differentiates from the closest sibling at the end ('For a one-off analysis write-up use `share_artifact` instead'), so an agent can separate the two without reading either 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?

States an explicit precondition ('Only call this when the user has explicitly asked to share or publish'), a gating mechanism (`user_request` verbatim or the tool refuses), and a named alternative for a different need (`share_artifact` for one-off write-ups). It even resolves an edge case by declaring that a request for an SEO/search-friendly link counts as asking to share.

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.