Skip to main content
Glama

NEM Explorer (ScadaMiner)

list_live_queries

Read-onlyIdempotent

Every live query URL this user has, with what each is called, whether it is pinned or expiring, how often it has been fetched, and whether its SQL has started failing. Use it to answer "what live links do I have", to find the one a user means before pinning or revoking it, and to explain a chart of theirs that has stopped updating.

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_live_queries"
  }
}

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

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the description's contribution is the content of the response — per-URL name, pin/expiry status, fetch frequency and failure state. That adds real behavioral context beyond the structured fields, though it says nothing about result size or ordering.

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?

One sentence, front-loaded with the returned resource and immediately followed by the situations that select it. Dense but every clause carries information; nothing is repeated from the annotations.

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

Completeness4/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 correctly takes on the burden of describing return fields, and it does so for a simple read-only list tool with one optional parameter. Only minor gaps remain, such as whether the list is bounded or ordered.

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?

The single optional question_id is fully documented in the schema (100% coverage) including its UUID format and attribution effect. The description adds nothing about it, which is acceptable but not above 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+resource (list every live query URL for this user) and it enumerates the returned attributes — name, pinned/expiring state, fetch count, SQL failure status. That is enough to tell it apart from list_dashboards or list_results 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 Guidelines4/5

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

Gives three concrete use cases, including the lookup-then-pin/revoke workflow, which implicitly routes the agent to pin_live_query. It does not explicitly name an alternative tool or state when not to use it, so it falls short of a full 5.

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.